Skip to content
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

chore(deps): update k8s deps #44

Merged
merged 1 commit into from
Dec 4, 2023
Merged

Conversation

flavio
Copy link
Member

@flavio flavio commented Dec 4, 2023

Update the following kubernetes dependencies together, doing that on an individual level will cause everything to break

  • apimachinery
  • client-go
  • controller-runtime

The update to latest version of controller-runtime required some changes to the code used to initialize our Manager, more specifically to the configuration options:

  • Port: this was the port used by the webhook server ran by the controller. The option is gone now, given we don't have a webhook endpoint I just removed that.
  • MetricsAddress: this has now been moved under Metrics, which holds the configuration of the metrics server. I've moved the configuration over there
  • Namespace: this option is gone. Now there's a more flexible (and IMHO confusing) way to configure the cache of the Kubernetes client. I've adapted the init code to achieve the same result as before: ensure only resources under the kwasm Namespace are watched. Cluster-wide resources, like Node, are not affected by this change; everything stays the same for them

Update the following kubernetes dependencies together, doing that on an
individual level will cause everything to break

- apimachinery
- client-go
- controller-runtime

The update to latest version of controller-runtime required some changes
to the code used to initialize our `Manager`, more specifically to the
configuration options:

* `Port`: this was the port used by the webhook server ran by the
  controller. The option is gone now, given we don't have a webhook
  endpoint I just removed that.
* `MetricsAddress`: this has now been moved under `Metrics`, which holds
  the configuration of the metrics server. I've moved the configuration
  over there
* Namespace: this option is gone. Now there's a more flexible (and IMHO
  confusing) way to configure the cache of the Kubernetes client. I've
  adapted the init code to achieve the same result as before: ensure
  only resources under the `kwasm` Namespace are watched. Cluster-wide
  resources, like Node, are not affected by this change; everything
  stays the same for them

Signed-off-by: Flavio Castelli <[email protected]>
Copy link

@Mossaka Mossaka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@0xE282B0
Copy link
Member

0xE282B0 commented Dec 4, 2023

Thank you!

@0xE282B0 0xE282B0 merged commit 49fbed8 into KWasm:main Dec 4, 2023
4 checks passed
@flavio flavio deleted the update-k8s-deps branch December 5, 2023 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants