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

Set Cron* types and defaults to v1beta1 #88

Merged
merged 2 commits into from
Nov 17, 2019

Conversation

JamesGuthrie
Copy link
Contributor

According to the Kubernetes documentation 1:

Note: CronJob resource in batch/v2alpha1 API group has been deprecated
starting from cluster version 1.8. You should switch to using
batch/v1beta1, instead, which is enabled by default in the API server.
Examples in this document use batch/v1beta1 in all examples.

This should fix the problem reported in #81

Copy link
Contributor

@Gabriella439 Gabriella439 left a comment

Choose a reason for hiding this comment

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

I'll merge this tomorrow unless anybody objects

@JamesGuthrie
Copy link
Contributor Author

Actually after having looked at something linked by @f-f in #81 it looks like it would also be necessary to modify dhall-kubernetes-generator/src/Dhall/Kubernetes/Data.hs in order to exclude the v2alpha1 versions instead of v1beta1, otherwise these changes will be overridden on the next generation.

According to the Kubernetes documentation [1]:

Note: CronJob resource in batch/v2alpha1 API group has been deprecated
starting from cluster version 1.8. You should switch to using
batch/v1beta1, instead, which is enabled by default in the API server.
Examples in this document use batch/v1beta1 in all examples.

[1]: https://kubernetes.io/docs/tasks/job/automated-tasks-with-cron-jobs/
@JamesGuthrie
Copy link
Contributor Author

@Gabriel439 I've updated dhall-kubernetes-generator/src/Dhall/Kubernetes/Data.hs, but it seems to have had an impact on the actual contents of the defaults.dhall file, which may result in this breaking backwards-incompatibility. I don't know if this is a problem for dhall-kubernetes.

@Gabriella439
Copy link
Contributor

@JamesGuthrie: I don't think that is an issue. We should expect this to change the hash since the contents of the resource include the apiVersion

I'll merge this tomorrow if nobody objects

@Gabriella439 Gabriella439 merged commit 2fb32a4 into dhall-lang:master Nov 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants