Skip to content
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

Project Network Isolation not available for downstream cluster in GUI #10620

Open
caduceus4 opened this issue Jun 14, 2023 · 1 comment
Open
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this

Comments

@caduceus4
Copy link

Rancher Server Setup

  • Rancher version: 2.7.3
  • Installation option (Docker install/Helm Chart):Helm chart for rancher gui, rpm for k3s

Information about the Cluster

  • Kubernetes version: 1.25.7
  • Cluster Type (Local/Downstream): Downstream/imported

User Information

  • What is the role of the user logged in? Admin

Describe the bug
I
have rancher 2.7.3 with an rke cluster running kubernetes 1.25.7 as the storage for downstream/imported clusters
The imported/downstream cluster is rke2, 1.25.7

I want to enable PNI, project Network Isolation.

There is no option to do so in the GUI when I edit the cluster config. If I use the downstream cluster kubeconfig, and do:

kubectl edit cluster.management.cattle.io/local

I can change enableNetworkPolicy to true and save it, but the 'hn' network policies are never added. it appears this particular resource is not really used.

What I had to do was view the cluster yaml in the gui. The yaml has a name not (apparently) used elsewhere, for me it was something
like:

name: c-m-2kcjjxdd

Then, using a kubeconfig file from the primary cluster:

kubectl edit cluster.management.cattle.io/c-m-2kcjjxdd

and set enableNetworkPolicy to true and save it. The 'hn' network policies for PNI were then added shortly thereafter

Expected Result

PNI should be available when editing a downstream cluster in the rancher gui

@skanakal skanakal transferred this issue from rancher/rancher Mar 14, 2024
@github-actions github-actions bot added [zube]: To Triage QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this and removed [zube]: To Triage labels Mar 14, 2024
@skanakal
Copy link
Contributor

It would appear that it's a UI issue...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

3 participants