canonical / knative-operators

Charmed Knative Operators
Apache License 2.0
1 stars 2 forks source link

chore: bump knative-eventing 1.8.0 -> 1.10.1 #155

Closed DnPlas closed 1 year ago

DnPlas commented 1 year ago

Bump the default version from 1.8.0 to 1.10.1

Fixes #144

orfeas-k commented 1 year ago

Hey I tried deploying locally on a multipass VM and I see the following in namespace knative-eventing.

NAME                                   READY   STATUS    RESTARTS   AGE
eventing-webhook-85d4bb4f7f-l5q6t      0/1     Pending   0          14m
mt-broker-filter-7646b96bc-wflwr       0/1     Pending   0          14m
mt-broker-ingress-7796bbd96d-qkcf7     0/1     Pending   0          14m
mt-broker-controller-d47b5c5c9-vlrsc   0/1     Pending   0          14m
imc-controller-6589ffd868-k96jb        1/1     Running   0          14m
imc-dispatcher-54bffbc7d5-t74lt        1/1     Running   0          14m
eventing-controller-69f9fbd68b-xzq8j   1/1     Running   0          14m

This could be a false alert and it could be machine limitations (small VM) since I don't see any errors other than this in the deployment's conditions. I 'll try to confirm later today in a larger VM and let you know, please wait before merging it

Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      False   MinimumReplicasUnavailable
  Progressing    False   ProgressDeadlineExceeded
orfeas-k commented 1 year ago

As I thought, it was an issue with my machine resources, manually deployed charms from PR on an EC2 instance and all deployment pods go to running. Approving as well

orfeas-k commented 1 year ago

Should we try reverting this change as well since we didn't see this error with knative-eventing?

DnPlas commented 1 year ago

Should we try reverting this change as well since we didn't see this error with knative-eventing?

yes, I think we are ready to do that. Let's submit a follow up PR.