-
Notifications
You must be signed in to change notification settings - Fork 173
FlinkDeployment: add flink-operator #9472
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
base: dev
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,202 @@ | |||
{{ if eq .Cluster.ConfigItems.flink_operator_enabled "true" }} |
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.
Please add this condition to all other resources, so that it becomes a "no-op" when disabled.
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.
Please also add all the guarded resources to https://github.com/zalando-incubator/kubernetes-on-aws/blob/dev/cluster/manifests/deletions.yaml. This way it's possible to turn it off after it was turned on (in case that's necessary).
kind: ConfigMap | ||
metadata: | ||
name: flink-operator-config | ||
namespace: kube-system |
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 wonder if it should rather be in its own namespace.
subjects: | ||
- kind: ServiceAccount | ||
name: flink | ||
namespace: kube-system |
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.
namespace should be removed for non-cluster-wide role bindings.
Adding Flink Operator controller to support FlinkDeployment