kubernetes-operator

Describe the feature/command for flytectl
Current way of flytectl upgrade is manual and the user needs to do a brew upgrade flytectl if he is mac user
or perform installer again and copy the binary
curl -s https://raw.githubusercontent.com/lyft/flytectl/master/install.sh | bash

flytectl version command already recommends whats the latest version .
eg :

flytectl version
A

monitored configMaps too.

`{
"configVersion":"v1",
"kubernetes":[
{
"apiVersion": "events.k8s.io/v1beta1",
"kind": "Event",
"namespace": {
"nameSelector": {
"matchNames": ["example-monitor-events"]
}
},
"fieldSelector": {
"matchExpressions": [
{
"field": "metadata.namespace",

Bug Report

What did you do?

$ git clone https://github.com/operator-framework/operator-lifecycle-manager.git
$ cd operator-lifecycle-manager
$ git describe 
v0.18.2-18-g20ded32d
$ ./scripts/install.sh v0.18.2

What did you expect to see?

The script ./scripts/install.sh v0.18.2 should return success code.

**What did you see instead? Under which circumstances

What would you like to be added:
Currently, kubectl kudo version only prints the current version of the KUDO CLI. It should also print the version of the KUDO controller if the con

Problem

K8s-event posting can fail to post an event (kind: Event) for any reasons, such as API rate limiting, temporary API failures (HTTP 5xx), control plane connectivity issues, SSL handshake failures, etc.

This leads to the events being lost, while they can represent some value. This applies both to the events created from the per-object logger messages (logger.info(...) from the

Currently, we have a simple approach where the operator simply watches the namespace it was created in. But in larger env, multi-namespaces are common. To create mysql cluster in any namespace, we broadly have two approaches (1) Make mysql-operator watch and create mysql clusters in any namespace (2) Continue with current model.
However, current approach is problematic when multiple namespaces ar

Related question GoogleCloudPlatform/flink-on-k8s-operator#114

Kubernetes 1.22 is coming and with a lot of API removals.

We're already using CustomResourceDefinition and {Validating,Admission}WebhookConfiguration resources in v1 but Capsule is managing also extensions/v1beta1 and networking.k8s.io/v1beta1. For these latest ones, we have to create a sort of check, disabl

Currently, SchemaHero assumes that every Postgres table will be deployed to the public schema. It should be possible to specify the schema when defining a table

I noticed that scanners and hooks use a different approach in their directory structure.
For the scanners there are subdirectories for parser and scanner (if existing) while the source code for the hook resides directly in its root directory.

I think we should introduce a hook directory inside each hook containing its source code to make their structure more clean.

Add example manifests for different persistence options (EBS volume / SSD mount / RAM disk)

Currently the env variables injected are specific to this docker image https://github.com/barney-s/docker-airflow

Align it with https://github.com/puckel/docker-airflow and make necessary changes in the operator to make it work with both.

related to GoogleCloudPlatform/airflow-operator#10

Currently the operator gets certain CRD values from the cluster during startup by get-ing the CRD (Operator.java:89). This means that the Operator needs access to list and get CRDs on the cluster to do this single operation.

We could store the CRD next to the source code in the jar file and read these values from there.