openshift

We could add support for the Rancher 2.2.x hardening guide. This would require a set of test files under a new cfg/rancher-2.2 directory.

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

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.

We are declaring certain specific configuration required for Kaniko directly in the IntegrationPlatformBuildSpec [1] and [2]. We should not let this details slip in the general configuration. A possible alternative is to provide a PublishStrategyOptions parameter with an open array/map of parameters that can be required by the strategy used (and where to move the aforementioned Kaniko para

/kind feature

Which functionality do you think we should add?

For outpu

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

Testing the newly implemented features of Eclipse JKube prior to a release is critical to deliver a great product.

For users reporting bugs, it might be helpful to validate that an issue was effectively fixed by being able to use the latest SNAPSHOT from the main/master branch.

Since we don't provide nightly builds (Jitpack seems like a much more powerful option), we need