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

[vdk-plugins] vdk-server: Pin kubernetes API version #919

Merged
merged 1 commit into from Jul 28, 2022

Conversation

doks5
Copy link
Contributor

@doks5 doks5 commented Jul 28, 2022

Currently, due to the fact that the control service's helm chart uses some
outdated APIs, vdk server --install cannot complete successfully, and throws
the below error:

Installing Control Service in Kind cluster...
-error: Stderr output: W0613 14:09:42.750230   43383 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
error: W0613 14:09:42.812327   43383 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
error: W0613 14:14:43.166567   43383 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
error: Error: INSTALLATION FAILED: release vdk failed, and has been uninstalled due to atomic being set: timed out waiting for the condition

In order for vdk-server to properly install the control service, we need to use older
kubernetes version

This change pins the version of kubernetes used by the kind cluster to 1.20.15 until
we adopt the new APIs in the control service helm chart.

Testing Done: Did vdk server --install locally and verified the control service is installed
correctly.

Signed-off-by: Andon Andonov andonova@vmware.com

Currently, due to the fact that the control service's helm chart uses some
outdated APIs, `vdk server --install` cannot complete successfully, and throws
the below error:
```
Installing Control Service in Kind cluster...
-error: Stderr output: W0613 14:09:42.750230   43383 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
error: W0613 14:09:42.812327   43383 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
error: W0613 14:14:43.166567   43383 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
error: Error: INSTALLATION FAILED: release vdk failed, and has been uninstalled due to atomic being set: timed out waiting for the condition
```

In order for vdk-server to properly install the control service, we need to use older
kubernetes version

This change pins the version of kubernetes used by the kind cluster to **1.20.15** until
we adopt the new APIs in the control service helm chart.

Testing Done: Did `vdk server --install` locally and verified the control service is installed
correctly.

Signed-off-by: Andon Andonov <andonova@vmware.com>
Copy link
Contributor

@ivakoleva ivakoleva left a comment

Choose a reason for hiding this comment

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

Is there any Kubernetes API (compatibility/support) versions docs/READMEs in the control service we can commentlink to ?

@doks5
Copy link
Contributor Author

doks5 commented Jul 28, 2022

Is there any Kubernetes API (compatibility/support) versions docs/READMEs in the control service we can commentlink to ?

@ivakoleva To the best of my knowledge, no.

@doks5 doks5 merged commit 7c41f56 into main Jul 28, 2022
@doks5 doks5 deleted the person/andonova/vdk-server-fix branch July 28, 2022 11:43
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.

None yet

3 participants