-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add istio dependency #7
Conversation
e9ad6f7
to
63d1722
Compare
- --upstream=http://127.0.0.1:8080/ | ||
- --logtostderr=true | ||
- --v=10 | ||
image: gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0 |
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 would remove the rbac proxy from the deployment. Maybe in other PR.
We removed it from the 3scale operator 3scale/3scale-operator#692
3scale Ops team has also removed the rbac proxy from their operator 3scale-ops/prometheus-exporter-operator#26
Check out for the reasons in the PRs
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.
Created follow up JIRA for this https://issues.redhat.com/browse/KUADRANT-32
Changes the default namespace from `kuadrant-operator-system` to `kuadrant-system`. The kuadrant controller is currently hard coded to use `kuadrant-system` when creating resources, so using it here ensures all kuadrant resources end up in the same ns. Will also make docs between the operator/controller/kuadrantcl repos more consistent.
Add istio makefile with targets to help install/uninstall istio using istoctl. The default is to install it in it's own namespace `istio-system` since this is more likely how it will be deployed in a real world scenario. The install is also using the `default` profile which installs an ingress controller into the istio namespace `istio-ingressgateway`. Any example port-forward commands need to point to this ingress service: ``` kubectl port-forward -n istio-system service/istio-ingressgateway 9080:80 ``` A temporary patch for the istio install and make targets to configure a hard coded kuadrant/authorino setup for dev/test purposes is also added. These are triggered using seperate make targets `istio-install-with-patch` and `post-deploy-hacks` and will be removed once the operator itself has taken over the responsibility of creating/configuring these resources.
63d1722
to
ed446ea
Compare
Update namespace to kuadrant-system
Changes the default namespace from
kuadrant-operator-system
tokuadrant-system
. The kuadrant controller is currently hard coded to usekuadrant-system
when creating resources, so using it here ensures all kuadrant resources end up in the same ns. Will also make docs between the operator/controller/kuadrantcl repos more consistent.Add istio make commands
Add istio makefile with targets to help install/uninstall istio using istoctl. The default is to install it in it's own namespace
istio-system
since this is more likely how it will be deployed in a real world scenario. The install is also using thedefault
profile which installs an ingress controller into the istio namespaceistio-ingressgateway
. Any example port-forward commands need to point to this ingress service:A temporary patch for the istio install and make targets to configure a hard coded kuadrant/authorino setup for dev/test purposes is also added. These are triggered using seperate make targets
istio-install-with-patch
andpost-deploy-hacks
and will be removed once the operator itself has taken over the responsibility of creating/configuring these resources.Verification
Deploy no OLM:
or
Deploy with OLM:
Check deployment:
Note: If you deployed via OLM there will be some additional deployments/pods in the kuadrant-system ns not listed here.