-
Notifications
You must be signed in to change notification settings - Fork 2
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
kserve-controller fails to be removed #131
Labels
bug
Something isn't working
Comments
Even after the refactoring introduced in #246 and #197, this issue is still present:
|
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5962.
|
The team suggests to either:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Removing kserve-controller will raise an error because it expects the istio-pilot:gateway-info relation to be present. This is caused by how the resources are rendered in preparation for removal. The context for rendering these Kubernetes resources is tightly coupled to the presence of certain relations.
Steps to reproduce
juju deploy kserve-controller --channel 0.11/stable --trust
orjuju deploy kserve-controller --channel latest/edge --trust
juju istio-pilot --channel 1.17/stable --trust
andjuju istio-gateway istio-ingressgateway --channel 1.17/stable --trust --config kind=ingress
juju deploy knative-serving --channel 1.10/stable --trust
andjuju deploy knative-operator --channel 1.10/stable --trust
juju config knative-serving namespace="knative-serving" istio.gateway.namespace=kubeflow istio.gateway.name=istio-gateway
juju remove-application kserve-controller
Environment
microk8s 1.29-strict/stable
microk8s addons: dns hostpath-storage metallb:10.64.140.43-10.64.140.49
juju 3.4/stable (3.4.4)
The text was updated successfully, but these errors were encountered: