openshift

For the next version 0.7.0 we are going to deprecated commands master and node as mentioned before aquasecurity/kube-bench#919

Not sure what the error is, but lint passes in the CI and locally even if exported structs dont have comments.
Most probably, it's an issue with the golangci yaml config we use.

Also we use revive instead of golint (which is deprecated), may be some setting in revive needs to be enabled?

If we check the goreport card, we can see the issues: https://goreportcard.com/report/github.com/jenkins

Hi,
This is a useful tool for any DevOps/SRE teams managing K8S clusters and apps.
One question though, will this be able to detect changes to Secrets stored in an external store like the GoDday one or the HashiCorp Vault.
thanks,
KK

I wonder if it's worth to develop a self message in Kiali checking the Istio version used.

That would help users to be aware if they are trying to deploy Kiali in a non compatible Istio version and save some time while troobleshooting.

$ minishift status
Minishift:  Running
Profile:    minishift
OpenShift:  Stopped
DiskUsage:  ERR of

perhaps this is related to the error state from the OpenShift isRunning check

We're already on Java 8 and we can use this diamond operator which was introduced in Java 7. Yet, there are lots of occurrences in code where we're still not using it. For more information about this, see this Sonar rule[0]

In case anyone is interested in fixing this, you can check all the occurrences where diamond operator could be used here[1]

[0] https://sonarcloud.io/organizations/fabric

I'm in the app folder.
I mkdir exports to make an export folder.
I run rake evm:export:service_dialogs -- --directory exports
I get back:

(in /var/www/miq/vmdb)
Error: argument --directory Destination directory must exist.
Try --help for help.

How can this be? I can ls and see my exports folder in this directory.

The operator prints periodically this info:

{"level":"info","ts":1623416979.434832,"logger":"camel-k","msg":"could not find any knative type in namespace camel, last error was: services.serving.knative.dev is forbidden: User \"system:serviceaccount:camel:camel-k-operator\" cannot list resource \"services\" in API group \"serving.knative.dev\" in the namespace \"camel\""}

It looks l

similarly to redhat-developer/odo#4861

Odo should not display SBO in odo catalog list services as the ServiceBinding should not be created by odo service creates

/kind feature
/priority medium

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

Test cases are failing for status pages which reflect that there is some API change from the service providers. We should update our implementation for handling status pages and fix those test cases.

Is your feature request related to a problem? Please describe.

No

Describe the solution you'd like

After some searching for a public dashboard for the grafana operator internal metrics, i was not able to find one.

Is there any already existing?

Describe alternatives you've considered

Building one (when there is some spare time)

Description

We have this usage of AssertJ where we're asserting a map's size:
https://github.com/eclipse/jk