-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPBUGS-18907: add KAS endpoints to Except in router egress rule #3007
OCPBUGS-18907: add KAS endpoints to Except in router egress rule #3007
Conversation
Skipping CI for Draft Pull Request. |
@sjenning: This pull request references Jira Issue OCPBUGS-17827, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sjenning The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@sjenning: This pull request references Jira Issue OCPBUGS-18907, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (jiezhao@redhat.com), skipping review request. The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/hold |
I added a commit to include private router in the e2e validation |
/test e2e-aws |
Because changes to the kas endpoints resource should result in updated policy, we should be watching endpoints in the hostedcontrolplane controller. /hold |
edccc4a
to
00ccb33
Compare
@@ -227,6 +227,7 @@ func (r *HostedClusterReconciler) managedResources() []client.Object { | |||
&corev1.Namespace{}, | |||
&corev1.ServiceAccount{}, | |||
&corev1.Service{}, | |||
&corev1.Endpoints{}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should follow up to filter events for only "kubernetes" endpoint in enqueueHostedClustersFunc
then also consider only caching that resource by letting ObjectSelector to filte by field metadata.Name = "kubernetes"
/hold cancel |
00ccb33
to
39d187c
Compare
AWS IPI failure |
/lgtm |
@sjenning: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@sjenning: Jira Issue OCPBUGS-18907: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-18907 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-4.14 |
@sjenning: new pull request created: #3010 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
…nshift#3007) * add KAS endpoints to Except in router egress rule * Add private router to EnsureLimitedEgressTrafficToManagementKAS e2e test --------- Co-authored-by: enxebre <alberto.garcial@hotmail.com>
Even though the
router
does not have the KAS mgmt label, it can still access the KAS because theprivate-router
NetworkPolicy allows it.