Skip to content

[release-2.1] fix: allow egress to Kubernetes API server on port 6443 [RHDHBUGS-3926] - #3830

Merged
rm3l merged 2 commits into
redhat-developer:release-2.1from
openshift-cherrypick-robot:cherry-pick-3814-to-release-2.1
Oct 13, 2026
Merged

rm3l merged 2 commits into
redhat-developer:release-2.1from
openshift-cherrypick-robot:cherry-pick-3814-to-release-2.1

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown
Contributor

This is an automated cherry-pick of #3814

/assign rm3l

rm3l added 2 commits October 13, 2026 07:13
Plugins that query cluster resources (Tekton, ArgoCD/GitOps, Topology,
KServe model catalog, and any catalog provider or frontend plugin that
lists or watches Kubernetes objects) need to reach the API server. On
OpenShift and kubeadm clusters the API server listens on port 6443,
which was blocked by the default-deny NetworkPolicy.

Add port 6443 alongside the existing port 443 in the allow-https-egress
policy. The rule has no destination selector, matching the existing 443
pattern — port 6443 is exclusively used by kube-apiserver, and RBAC on
the ServiceAccount is the real access-control boundary.
@sonarqubecloud

Copy link
Copy Markdown

@openshift-ci openshift-ci Bot added the lgtm label Oct 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor

✅ PR images built and pushed successfully!

Images are available for testing (expires in 7 days):

Image Full tag PR tag
Operator quay.io/rhdh-community/operator:2.1.0-pr-3830-4efbc43 quay.io/rhdh-community/operator:2.1.0-pr-3830
Bundle quay.io/rhdh-community/operator-bundle:2.1.0-pr-3830-4efbc43 quay.io/rhdh-community/operator-bundle:2.1.0-pr-3830
Catalog quay.io/rhdh-community/operator-catalog:2.1.0-pr-3830-4efbc43 quay.io/rhdh-community/operator-catalog:2.1.0-pr-3830

@rm3l
rm3l merged commit 7b52845 into redhat-developer:release-2.1 Oct 13, 2026
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants