GitOps support - Githubissues

solo-io / service-mesh-extensions

A public registry of all service mesh extensions and other content for the Service Mesh Hub.

Apache License 2.0

14 stars 6 forks source link

GitOps support #64

Open derrickburns opened 5 years ago

derrickburns commented 5 years ago

@yuval-k I love your service mesh hub, but I cannot use it in its current form.

I need support for GitOps. For the Service Mesh Hub, this means that instead of writing updates directly to a cluster, the Hub writes/updates manifests to a Git(Hub) repo. This provides an audit trail, which we need for HIPAA compliance.

rickducott commented 5 years ago

Thanks! I am working on a clientside renderer for this exact use case, would love to share some preliminary work with you for feedback in a few days.

derrickburns commented 5 years ago

Great! Count me in!

derrickburns commented 5 years ago

@rickducott Ping

rickducott commented 5 years ago

Sorry about the delay, fell behind here prepping for a Gloo release, should be back on this shortly.

joekelley commented 5 years ago

Hi @derrickburns, today we added two commands to the Service Mesh Hub cli to facilitate client-side rendering. Run the cli with go run pkg/cli/cmd/main.go ….

render will prompt you for the application, version, flavor, and additional parameters needed to render manifests. Optionally specify an output file with -o and/or an installation spec file with -i.
prepare -i <destination> will output an installation spec file that contains all the necessary values for rendering manifests. Pass this file to render with -i to bypass configuration.

Please let us know what you think!

derrickburns commented 5 years ago

Awesome! Will do.

Derrick Burns On Aug 13, 2019, 11:54 AM -0700, Joe Kelley notifications@github.com, wrote:

Hi @derrickburns, today we added two commands to the Service Mesh Hub cli to facilitate client-side rendering. Run the cli with go run pkg/cli/cmd/main.go ….

• render will prompt you for the application, version, flavor, and additional parameters needed to render manifests. Optionally specify an output file with -o and/or an installation spec file with -i. • prepare -i will output an installation spec file that contains all the necessary values for rendering manifests. Pass this file to render with -i to bypass configuration.

Please let us know what you think! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.