RELEASE.md

Release

osd-network-verifier will follow semantic versioning

Considerations around changes

These changes don't automatically mean a change is a breaking or significant change, but should be taken into consideration:

• The various input verifier structs in ./pkg/verifier/package_verifier.go are exported and consumed downstream. Breaking changes to that input struct should be considered breaking changes for osd-network-verifier.
• New AMIs in ./pkg/probes/curl/machine_images.go, especially as the result of security fixes.
• New cloud IAM requirements/new cloud infrastructure to provision

Testing changes

For now, this is mostly manual. It's important to validate that these scenarios are working before making a new release:

• The cloudMachineImageMap values in ./pkg/probes/curl/machine_images.go should be updated to match what is in the console output for the most recent golden-ami build.
  • Note - if the above build is broken due to ResourceLimitExceeded issues, you will have to clean up the AMI image repository by running the cleangoldenami module, and then re-running the Jenkins build.
• Build the integration binary by running go build from the /integration folder. Then use this binary to test both the aws and hostedcluster configurations as shown below. For more information on setting up integration tests, see the integration README.
  • ./integration --platform aws-classic
  • ./integration --platform aws-hcp
• egress test in AWS with a cluster-wide proxy
• egress test on GCP This should be added back when GCP support is functional again

After a new release has been created, please create an MR for the downstream projects to use the latest verifier version. The latest version can be fetched with go get github.com/openshift/osd-network-verifier@<the new tag>

• Cluster Service (https://gitlab.cee.redhat.com/service/uhc-clusters-service)
• osdctl (https://github.com/openshift/osdctl)
• Configuration Anomaly Detection (https://github.com/openshift/configuration-anomaly-detection)