Jose R. Gonzalez

Bump! It would nice to see restricted-friendly examples. Would prefer to see the guestbook example use a high-numbered port at the very least as it seems like the quickest path.

@hect1995 The simplest way I've found is just to bind to a high-numbered port in the sample application, and pass that through to the manifests.

Just wanted to share possible implementations here. Have not submitted a PR as these requirements and a path forward haven't been hashed out here yet. https://github.com/komish/community/commit/97f942a892fea3abbf86a5305cffece745be2b46 https://github.com/komish/community/commit/8f5d53cdbc865fa71de3996e727c8061fe678d41 These aren't the...

Hi @AMecea! I understand that Orchestrator is a stateful component and is primarily the motivation behind making use of the statefulset as the operator deployment methology. Could you give some...

> @brettkromkamp I don't want to chalk it up to PostgreSQL just yet. Using the Docker configuration, I _should_ be seeing something at 127.0.0.1:5000 or localhost:5000 but don't. I was...

@machawk1 in the meantime while #21 is getting resolved, just add the these lines to your settings.ini. https://github.com/brettkromkamp/contextualise/blob/master/settings-sample.ini#L14-L15

Red Hat submissions have an automated workflow. I can't see us prioritizing some community submissions over others just because the listed githubUsernames contain Red Hatters at this time. I'll leave...

It's certainly technically feasible. We mostly need to evaluate the historical reasons for manual approval. At the moment, it's not a priority, but we can consider it in the future.

Pinging the owner: @phracek can you take a look? https://github.com/openshift-helm-charts/charts/tree/main/charts/redhat/redhat/httpd-template

I believe we already use chart-releaser for some things in the pipeline. It's worth noting that the `helm repo index` command also exists for this purpose. I'm thinking part of...