Failure executing GET for v1beta1 ingress on K8s v1.22
Closed this issue · 3 comments
dev-rowbot commented
Hi,
I am trying to deploy the shinyproxy operator to EKS => Server Version: v1.22.6-eks-7d68063
My deployment is based on the 1-namespaced-hpa example. I have tweaked it a bit to turn it into a helm chart but it is essentially the same deployment.
The operator fails with:
09:50:05.906 [main ] DEBUG io.fa.ku.cl.Config - Trying to configure client from Kubernetes config...
09:50:05.910 [main ] DEBUG io.fa.ku.cl.Config - Did not find Kubernetes config at: [/home/shinyproxy-operator/.kube/config]. Ignoring.
09:50:05.911 [main ] DEBUG io.fa.ku.cl.Config - Trying to configure client from service account...
09:50:05.911 [main ] DEBUG io.fa.ku.cl.Config - Found service account host and port: 172.20.0.1:443
09:50:05.912 [main ] DEBUG io.fa.ku.cl.Config - Found service account ca cert at: [/var/run/secrets/kubernetes.io/serviceaccount/ca.crt].
09:50:05.913 [main ] DEBUG io.fa.ku.cl.Config - Found service account token at: [/var/run/secrets/kubernetes.io/serviceaccount/token].
09:50:05.913 [main ] DEBUG io.fa.ku.cl.Config - Trying to configure client namespace from Kubernetes service account namespace path...
09:50:05.914 [main ] DEBUG io.fa.ku.cl.Config - Found service account namespace at: [/var/run/secrets/kubernetes.io/serviceaccount/namespace].
09:50:06.912 [main ] INFO eu.op.sh.Operator - Using NAMESPACED for property SPO_MODE
09:50:06.913 [main ] INFO eu.op.sh.Operator - Using false for property SPO_DISABLE_SECURE_COOKIES
09:50:06.915 [main ] INFO eu.op.sh.Operator - Using 0 for property SPO_PROBE_INITIAL_DELAY
09:50:06.915 [main ] INFO eu.op.sh.Operator - Using 0 for property SPO_PROBE_FAILURE_THRESHOLD
09:50:06.916 [main ] INFO eu.op.sh.Operator - Using 3 for property SPO_PROBE_TIMEOUT
09:50:06.916 [main ] INFO eu.op.sh.Operator - Using 60 for property SPO_STARTUP_PROBE_INITIAL_DELAY
09:50:06.917 [main ] INFO eu.op.sh.Operator - Using -1 for property SPO_PROCESS_MAX_LIFETIME
09:50:06.918 [main ] INFO eu.op.sh.Operator - Using ALL for property SPO_LOG_LEVEL
09:50:06.921 [main ] INFO eu.op.sh.Operator - Running in NAMESPACED mode
09:50:06.922 [main ] INFO eu.op.sh.Operator - Using namespace : shinyproxy
09:50:07.217 [main ] INFO eu.op.sh.Operator - Starting background processes of ShinyProxy Operator
Warning: could not check whether ShinyProxy CRD exits.
This is normal when the ServiceAccount of the operator does not have permission to access CRDs (at cluster scope).
If you get an unexpected error after this message, make sure that the CRD exists.
09:50:11.622 [main ] DEBUG eu.op.sh.co.ShinyProxyListener - [shinyproxy/shinyproxy/global] [Event/Add]
09:50:11.716 [main ] DEBUG .fa.ku.cl.ds.in.AbstractWatchManager - Watching https://172.20.0.1/apis/openanalytics.eu/v1/namespaces/shinyproxy/shinyproxies?resourceVersion=28823137&watch=true...
09:50:11.959 [/172.20.0.1/...] DEBUG ku.cl.ds.in.WatcherWebSocketListener - WebSocket successfully opened
09:50:13.116 [main ] TRACE eu.op.sh.co.ResourceListener - ReplicaSet::OnAdd shinyproxy-operator-569545f86c
09:50:13.119 [main ] TRACE eu.op.sh.co.ResourceListener - ReplicaSet::OnAdd shinyproxy-operator-84f6f6596f
09:50:13.119 [main ] TRACE eu.op.sh.co.ResourceListener - ReplicaSet::OnAdd shinyproxy-operator-957686b59
09:50:13.120 [main ] TRACE eu.op.sh.co.ResourceListener - ReplicaSet::OnAdd shinyproxy-operator-cdc75d695
09:50:13.120 [main ] TRACE eu.op.sh.co.ResourceListener - ReplicaSet::OnAdd shinyproxy-operator-redis-6d8c5df48f
09:50:13.120 [main ] TRACE eu.op.sh.co.ResourceListener - ReplicaSet::OnAdd shinyproxy-operator-redis-c9849bc8b
09:50:13.120 [main ] TRACE eu.op.sh.co.ResourceListener - ReplicaSet::OnAdd shinyproxy-operator-skipper-55744fbfbf
09:50:13.121 [main ] TRACE eu.op.sh.co.ResourceListener - ReplicaSet::OnAdd shinyproxy-operator-skipper-584dbc94
09:50:13.121 [main ] TRACE eu.op.sh.co.ResourceListener - ReplicaSet::OnAdd shinyproxy-operator-skipper-864b4c945
09:50:13.122 [main ] DEBUG .fa.ku.cl.ds.in.AbstractWatchManager - Watching https://172.20.0.1/apis/apps/v1/namespaces/shinyproxy/replicasets?resourceVersion=28823154&watch=true...
09:50:13.315 [/172.20.0.1/...] DEBUG ku.cl.ds.in.WatcherWebSocketListener - WebSocket successfully opened
09:50:13.514 [main ] TRACE eu.op.sh.co.ResourceListener - Service::OnAdd shinyproxy-operator
09:50:13.515 [main ] TRACE eu.op.sh.co.ResourceListener - Service::OnAdd shinyproxy-operator-skipper
09:50:13.519 [main ] DEBUG .fa.ku.cl.ds.in.AbstractWatchManager - Watching https://172.20.0.1/api/v1/namespaces/shinyproxy/services?resourceVersion=28823159&watch=true...
09:50:13.809 [/172.20.0.1/...] DEBUG ku.cl.ds.in.WatcherWebSocketListener - WebSocket successfully opened
09:50:13.824 [main ] TRACE eu.op.sh.co.ResourceListener - ConfigMap::OnAdd kube-root-ca.crt
09:50:13.825 [main ] DEBUG .fa.ku.cl.ds.in.AbstractWatchManager - Watching https://172.20.0.1/api/v1/namespaces/shinyproxy/configmaps?resourceVersion=28823162&watch=true...
09:50:14.009 [/172.20.0.1/...] DEBUG ku.cl.ds.in.WatcherWebSocketListener - WebSocket successfully opened
09:50:14.020 [main ] WARN io.fa.ku.cl.in.VersionUsageUtils - The client is using resource type 'ingresses' with unstable version 'v1beta1'
09:50:14.025 [main ] WARN eu.op.sh.Main - Kubernetes Client Exception : Failure executing: GET at: https://172.20.0.1/apis/networking.k8s.io/v1beta1/namespaces/shinyproxy/ingresses. Message: the server could not find the requested resource. Received status: Status(apiVersion=v1, code=404, details=StatusDetails(causes=[], group=null, kind=null, name=null, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=the server could not find the requested resource, metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=NotFound, status=Failure, additionalProperties={}).
The readme shows a tick next to version 1.1.0 (not yet released) for k8s version 1.22. Is there any way we can get that version (even a pre-release) to see if it will resolve the issue?
dev-rowbot commented
For info, I have pushed the changes required to get skipper working, you can view the diff here:
LEDfan commented
The readme shows a tick next to version 1.1.0 (not yet released) for k8s version 1.22. Is there any way we can get that version (even a pre-release) to see if it will resolve the issue?
Just to make it clear for you, we did not yet start the work on supporting 1.22, so we are thankful for your PR. The section in the README was more to inform users about our plans indeed.