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

[Docs] Change order of cluster resources config example #4372

Closed
2 tasks done
neverett opened this issue Nov 6, 2023 · 1 comment · Fixed by #4373
Closed
2 tasks done

[Docs] Change order of cluster resources config example #4372

neverett opened this issue Nov 6, 2023 · 1 comment · Fixed by #4373
Assignees
Labels
documentation Improvements or additions to documentation untriaged This issues has not yet been looked at by the Maintainers

Comments

@neverett
Copy link
Contributor

neverett commented Nov 6, 2023

Description

The copy-pastable config in the Cluster Resources section of the Configuring Custom K8s Resources doc cause an error when uctl update cluster-resource-attribute --attrFile cra.yaml is run. Changing the ordering in the example to the following will enable it to work with either uctl or flytectl:

domain: development
project: flyteexamples
attributes:
    projectQuotaCpu: "1000"
    projectQuotaMemory: 5Ti

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes
@neverett neverett added documentation Improvements or additions to documentation untriaged This issues has not yet been looked at by the Maintainers labels Nov 6, 2023
Copy link

welcome bot commented Nov 6, 2023

Thank you for opening your first issue here! 🛠

@neverett neverett changed the title [Docs] Change order of attributes in cluster resources config example [Docs] Change order of cluster resources config example Nov 6, 2023
@neverett neverett self-assigned this Nov 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation untriaged This issues has not yet been looked at by the Maintainers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant