You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 25, 2021. It is now read-only.
The current package init command expects to be invoked from a kubebuilder project.
Tempate stacks can be created with only helm3 or kustomize files.
What does it look like when it's done?
The init command should offer arguments to simplify the experience when working in this environment.
Should this be the default mode? Should the environment be detected (and overridable)?
The text was updated successfully, but these errors were encountered:
displague
changed the title
stack init should offer tempate stack options to init from helm3 or kustomize
package init should offer tempate stack options to init from helm3 or kustomize
Jul 8, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What is the problem?
The current
package init
command expects to be invoked from a kubebuilder project.Tempate stacks can be created with only helm3 or kustomize files.
What does it look like when it's done?
The init command should offer arguments to simplify the experience when working in this environment.
Should this be the default mode? Should the environment be detected (and overridable)?
The text was updated successfully, but these errors were encountered: