kubectl-operator

kubectl-operator copied to clipboard

Allow installing into global-operator group

2

The possibleInstallModes method doesn't deal with the special case of a target namespace being the empty string, so validation fails when installing to the global operator group. E.g. ❯ kubectl...

kouk

operator install: honor operatorframework.io/suggested-namespace

2

**Description:** Updates `kubectl operator install` to honor CSVs that provide an `operatorframework.io/suggested-namespace` annotation. **Motivation:** Closes #50 /hold I can't find any upstream documentation for `operatorframework.io/suggested-namespace`, so I'm somewhat concerned that...

joelanford

OLM sometimes creates two install plans for a subscription

1

I ran: ``` kubectl operator install etcd -w "default" -C ``` This seems to result in a successful installation, but there's an extra install plan in the namespace for etcd,...

joelanford

Feature req: Honor operatorframework.io/suggested-namespace

10

I have been working on an operator which is listed in the Operator Hub catalog, and it has some resources (clusterrolebinding) which are expected to be created for service accounts...

kingdonb

[RFE] Autocompletion for commands

2

Story: A user would like to be able to get the standard kubectl autocomplete experience when using the plug-in. Open question: how difficult is this to implement?

exdx

Add debug command to root command for installation debugging

1

OLM users right now have a hard time debugging operator installations that have gone awry. They are required to dig deep into internal APIs, such as InstallPlans, to piece together...

exdx

Right now, the `kubectl operator` uses an error-prone shortcut to enable users to provide just a `--version` flag to the `install` subcommand rather than the full starting CSV. It starts...

joelanford

Related to #1 and #2, when installing operators at non-channel heads, it is not possible to determine the set of supported install modes in advance. This makes it possible for...

joelanford

The catalog source has several metadata fields in the spec that are optional, but nice to have for UX purposes, both on the command line and in a UI. These...

joelanford

Right now, `list-available ` can show the versions at each channel head for a particular package, but it doesn't seem possible to know earlier versions. Ideally, the packagemanifest API would...

joelanford