-
Notifications
You must be signed in to change notification settings - Fork 56
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
Simplify install #466
Simplify install #466
Conversation
rules: | ||
- apiGroups: [""] |
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.
This is a nice cleanup
I do think we need:
impersonate – users & groups
list – pods
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.
I think we still need services and pods too:
services, err := clientset.CoreV1().Services(namespace).List(context.TODO(), metav1.ListOptions{
LabelSelector: "app.kubernetes.io/instance=infra-engine",
})
componentPods, err := clientset.CoreV1().Pods("kube-system").List(context.TODO(), metav1.ListOptions{
LabelSelector: "component=kube-controller-manager",
})
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.
Yep! Add list - services
to that list
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.
services
list
is still part of the role; only services
get
was removed. Will add back users|groups
impersonate
and pods
list
This is great stuff! What would the new |
rules: | ||
- apiGroups: [""] |
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.
I think we still need services and pods too:
services, err := clientset.CoreV1().Services(namespace).List(context.TODO(), metav1.ListOptions{
LabelSelector: "app.kubernetes.io/instance=infra-engine",
})
componentPods, err := clientset.CoreV1().Pods("kube-system").List(context.TODO(), metav1.ListOptions{
LabelSelector: "component=kube-controller-manager",
})
@@ -1,8 +1,9 @@ | |||
apiVersion: rbac.authorization.k8s.io/v1 | |||
kind: Role | |||
metadata: | |||
name: infra-registry-secret-reader | |||
namespace: {{ .Release.Namespace }} | |||
name: {{ include "registry.fullname" . }} |
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.
Should we be more descriptive in the name of this role still?
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.
I think that depends on if we expect to add more roles for the registry. IMO keeping it simple and consistent produces the best experience for the user, i.e. if they want to know what permission infra-registry
has, they can get the role without first looking up what the role is called.
The omni chart is still a work in progress and I've split it off into a separate PR so this shouldn't require any README.md changes |
47d3a56
to
72ec675
Compare
72ec675
to
269acd6
Compare
269acd6
to
fae0f02
Compare
Role
shouldn't be necessary anymore since the engine is no longer being accessed through the proxyClusterRole
which has been briefly tested so it's possible some are still neededuser|group
impersonate
pods
list
services
get
ingresses
list
namespaces
list
Implement #465