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

Mega Feature: Add kro cli #138

Open
candonov opened this issue Nov 14, 2024 · 1 comment
Open

Mega Feature: Add kro cli #138

candonov opened this issue Nov 14, 2024 · 1 comment

Comments

@candonov
Copy link
Collaborator

candonov commented Nov 14, 2024

Feature Description

Problem Statement:
Add a cli for kro and integrate it with kubectl.

Proposed Solution:

The cli should support a diff functionality using --dry-run:

kubectl kro apply -f <updatdRG>.yaml --dry-run
kubectl kro apply -f <updatedInstance>.yaml --dry-run

It should also show the chain dependent resources of an instance and their statuses:

NAME                                  STATE    SYNCED   AGE
webappInstance                        ACTIVE   True     42h
       ├── deployment                 ACTIVE   True     42h
       ├── service                    ACTIVE   True     42h
       └── ingress                    ACTIVE   True     42h

Alternatives Considered:

Additional Context:

  • Please vote on this issue by adding a 👍 reaction to the original issue
  • If you are interested in working on this feature, please leave a comment
@candonov candonov changed the title Mega Feature: add kro cli Mega Feature: Add kro cli Nov 14, 2024
@amirahav
Copy link

amirahav commented Dec 9, 2024

We believe that the biggest benefits of having the CLI would be around schema validation, linting of the expression language, having an ability of doing a dry-run on the ResourceGroup as well as an ability to produce the complete CRD that would be generated by the ResourceGroup.

In addition, it would be beneficial if there would be a way to view the effects of changes to the ResourceGroup on the instances prior to the ResourceGroup changes being made. eg, there is a proposed change to the ResourceGroup it would be very helpful to know how that change would affect all the instances of that ResourceGroup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants