You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2023. It is now read-only.
Hi,
Is there any estimation when a new operator release is due? and also bundeled in the openshift operatorhub?
I wan to use the new operator with the 3.8 release, problem is this operator creates old CRD while 3.8 works with new CRD
I have tried installing the gatekeeper it self on openshift but im getting issues with SCC which are not specified in the docs
The text was updated successfully, but these errors were encountered:
Do you mean through the Red Hat Openshift operator hub? The next "downstream" release there will be delivered with a future version of ACM (date unconfirmed).
I've just updated the main branch to gatekeeper-3.8.1 and will push that to the release-0.3 and tag it for a 0.3.0-candidate.2 build. Would that be useful for you?
@thomasmckay Um I think so, I just need a new version from the operator hub, since the current available version is only 3.5.4 and its relatively old since there is no support for astrix with namespace exemptions, the crds are a version older
even updates to current openshift operator hub , version 4,8/4.7
is that something possible?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
Is there any estimation when a new operator release is due? and also bundeled in the openshift operatorhub?
I wan to use the new operator with the 3.8 release, problem is this operator creates old CRD while 3.8 works with new CRD
I have tried installing the gatekeeper it self on openshift but im getting issues with SCC which are not specified in the docs
The text was updated successfully, but these errors were encountered: