Alistair Hey
Alistair Hey
We can add a hidden command to build the template of a new command, for chart apps we only need to provide 4 things to get a "default" install done....
## Expected Behaviour Something like ``` arkade install issuer --type route53 --credentials-file ~/route53-creds ``` We have the manifests somewhere in the OFC / ofc-bootstrap archived repos. It would set secrets...
once support for the license being a secret is merged into the inlets-operator chart it would be good to support that here, so the license is not exposed in deployments...
It would be useful to have an E2E test solution for: * Installing an app (and possibly dependency apps, like for openfaas-ingress) on k3d * waiting for it to finish...
It might be useful to have a command that verifies that an app was installed correctly? like looking at the deployments/CRDs and making sure they have started? Plus we could...
If there's a merge commit pushed to a PR can we add a label and post a message to the PR from Derek saying that Merge Commits are not allowed,...
We need to move over to using GHCR images in the helm chart once the GH Actions migration has gone in Also, each release will build a new set of...
Currently only some of the deployment of OFC can be done using helm. We still rely on cloning this repo, applying overrides to the openfaas functions yaml files and env...
We should move OFC components to Go Modules. This will be a 2 (or more) part process where 1. first off we need a go.mod in each folder. 2. implement...
There has been requests to allow custom domains in OFC (https://github.com/openfaas/openfaas-cloud/issues/520) We now have FunctionIngress CRD provided by the IngressOperator provided as an option in the ofc-bootstrap installer. We could...