[minor] Support March Interim Catalog Update: 260318#212
Open
anilprajapatiibm wants to merge 2 commits intostablefrom
Open
[minor] Support March Interim Catalog Update: 260318#212anilprajapatiibm wants to merge 2 commits intostablefrom
anilprajapatiibm wants to merge 2 commits intostablefrom
Conversation
anilprajapatiibm
changed the title
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
1 participant
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.
Catalog: https://github.ibm.com/maximoappsuite/ibm-maximo-operator-catalog/pull/934
Address issue with kubernetes client and no_proxy
Emergency fix for operators explicitly installing mas-utils as this dependency was also including the kubernetes v35 library. This fix in the Dockerfile should be removed on the next 9.1.x release of ibm-mas.
Downgrade the Python kubernetes client to 33.1.0 as a temporary workaround for a proxy-related regression introduced in newer releases. Upstream issues report that versions 34.1.0+ can mishandle no_proxy, causing Kubernetes API requests that should bypass a configured proxy to be routed through it instead. In our OpenShift Ansible operator environment, this affects in-cluster API access when cluster-wide proxy variables are present. This change restores the previously working client version while we investigate if a longer-term fix: explicitly configuring kubernetes.core with K8S_AUTH_PROXY and K8S_AUTH_NO_PROXY is required rather than relying on inherited standard proxy environment variables.