-
Notifications
You must be signed in to change notification settings - Fork 107
Installing Knative-Serving to non-default namespace has incorrect kourier bootstrap #2049
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
Comments
@arsenetar You were right. I just found out that the namespace is hardcoded in the yaml of kourier.yaml as
I am thinking of how to to fix it. |
It is not quite intuitive for me to change the yaml and load in the operator to change a field but within the data of a configMap. I have got one solution right now to resolve it, though it may look ugly. The configuration is from a configmap. To change the configmap, you can edit your cr like this: It is dumping all configurations of the CM
|
I was thinking just adding an additional Transform to https://github.com/knative/operator/blob/main/pkg/reconciler/knativeserving/ingress/kourier.go would be the approach to take to set the value correctly. |
It was not easy, since this is the data of the whole configmap, not like a specific or single field we can target in other kubernetes objects. Not sure if you have any suggestions. |
Describe the bug
When deploying Knative-Serving to a non-default namespace (
knative-test
) the kourier bootstrap is still generated pointing the gateways to usenet-kourier-controller.knative-serving
for the xds cluster. This causes the gateways to not come up healthy.Expected behavior
Kourier is correctly configured to work in the namespace the components are deployed in. (Since the operator deploys kourier gateways in the same namespace as all the other components
net-kourier-controller
works for the address.)To Reproduce
Deploy Knative-Serving into a non-default namespace (
knative-test
) with kourier as ingress.Knative release version
Seems to impact all versions currently supported by the operator as they configure kourier the same.
Additional context
The text was updated successfully, but these errors were encountered: