OKDerators: Q on versionning, contribution, PR proposals ...

[titou10titou10]

I tried to install the "okd pipeline" operator from this catalog but hit a problem related to "StepAction version conversion not enabled..." (to be investigated)
The fact is that the operator deploys tekton pipelines v0.65.5, the "official" RH/OCP pipeline operator deploys v0.68.0 (with operator v1.18.0), the official tekton operator also deploys v0.68.0 (with operator v0.75.0). The current version of tekton pipeline is v0.70.0

I have no idea what are the rule for the okd operator versionning in this catalog. Should it follow RH/OCP operator releases or the base tekton operator release? Is there a governance that describe the policy?

I also have no idea on what to do to propose a PR to upgrade the version of the components of the operator (... to what version?)

ref: https://github.com/tektoncd/operator/releases

[GingerGeek]

Hi, just moving this discussion to the okd repo. I am in the process of doing housekeeping on the GitHub org as you have probably seen. One of the struggles in the WG is the many points/repos that people can engage.

I think all discussions/forum-like content we will try and keep in okd repo, I will disable discussions in other repos. Issues etc make sense in other repo.

With regards to this question... pinging @SupremeMortal

[GingerGeek]

This discussion followed on from comments from @ibotty and @titou10titou10 about wanting to get involved contributing

#456 (comment)

[ibotty]

I want to update the logging operator, but I don't have the a cluster yet to test my changes. I'd really like to have some official feedback if my work is going to be appreciated.

@GingerGeek, @SupremeMortal: If I create a PR with untested changes, can you (trigger to) run the pipelines to check whether it looks alright? Is there infrastructure in place for that? If not, what's missing?

When I get to it, I'll document on what I did and post it here for others to join the fun of chasing the official catalog.

[SupremeMortal]

My workflow is to build the operator, add it to a dev catalog, then test the functionality on a test cluster.

I am committing my build scripts to a separate branch in the okd-operator-pipeline repo until we're able to get CI setup on the CentOS build cluster we recently got access to.