kubernetes-operator

Describe the issue

Currently we run the Linter CI for golang repos using the golang-ci-linter binary. But according to the documentation it is faster and better to use the github action.
https://golangci-lint.run/usage/install/

The UX of all the error highlighting is also better.

What if we do not do this?

Finding linter errors is troublesome as users have to parse through the cons

monitored configMaps too.

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

Almost all CRD declared in operator lifecyle manager are in v1alpha1 version.
Until now it's enough but when it'll be migrated to v1, the conditions will have to respect conventions describe here:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties

This should be put in the backlog.

The current conditions are

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

For now, under "podSpec" - there is no way to set resources limits and requests for pt-heartbeat container from mysqlcluster's statefulset.

Please add option for pt-heartbeat like mysqlOperatorSidecarResources and metricsExporterResources.

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

kubectl schemahero get migrations command can output a long list of migrations, with potentially repeating names.

To find the right migration with a tool like grep, we need to look at the what schema files were changed to determine what the name of the migration would be.

It would be nice to list migrations sorted by timestamps or filter by migration state (open/approved/applied)

As a user of the secureCodeBox
I want to access the docs for the auto-discovery on the docs page
to be able to use configure and use it properly

• Include auto-discovery docs on the docs page
• Add a link to the docs page to the menu

I'm not sure right now how to specify NodePort with AWX operator. Its not mentioned in documentation.

spec:
tower_ingress_type: NodePort

Ok, but how to avoid random port assignment,

Usually I can do in service deployment something like:

spec:
  type: NodePort
  ports:
    - port: 80
      nodePort: 30080
      name: http
    - port: 443
      nodePort: 30443
      name

Most of the current use cases, automated tests and functional test scenarios were performed in context of 2 clusters only as it is most common and easier to test setup.

Meanwhile we need to be ready and test for >2 scenario cluster scenario.

This series of testing can reveal potential edge cases in current LB strategies implementation and can lead to LB logic extension and handling of >2 num

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