Open
Conversation
MCK 1.7.1 Release NotesOther Changes
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This change makes the operator proxy test more strict in order to better catch failures in configuring the automation agent for proxy access. It also runs them against Ops Manager, not just Cloud Manager to test the Ops Manager agent behavior as well.
This is achieved by a NetworkPolicy (via Calico) that allows the tested replica set pods to access only each other and the proxy pod. Failure to reconcile means that some component didn't pick up the proxy settings.
Currently this fails because the automation agent doesn't seem to respect the proxy environment variables defined by the operator. Adding the
-httpProxyagent flag in the replica set CR fixes that.Proof of Work
Successful* patch with
-httpProxyset.Failing patch with just the proxy environment variables.
* The non-static CloudQA variant fails because of a regression in the Cloud Manager automation agent's handling of proxy settings when downloading binaries.
Checklist
skip-changeloglabel if not needed