Does PipeCD conform to GitOps Principles? #2752
-
Hi, @nghialv, Thank you for your time. ❔ Does PipeCD conform to GitOps Principles? ❔ What are the definitions of the hashtag ❔ Perhaps PipeCD defines the word "GitOps" differently from panelists in Panel Discussion: OpenGitOps and the GitOps Working Group? Specifically, my concern about PipeCD's usage of the word "GitOps" is: Please correct me if my understanding is incorrect. My understanding is:
Thank you for answering my questions. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Hi, @lloydchang Firstly, thank you for your question. ❤️
Yes, I think that PipeCD conforms to those GitOps Principles.
I don't think there's that much of a difference. Can you tell me the difference you are thinking of? Please let me correct something about PipeCD in your comments.
No, PipeCD is not doing CIOps like that. As you know PipeCD has 2 components: control-plane and agent (piped).
By default, PipeCD continuously detects the drift to report/alert to users (by showing the diff on the web console, sending notification to Slack...). Currently, PipeCD does not re-apply (re-trigger the deployment) when detected a drift but we're on the way to support that. And actually, not all users want to enable that auto re-applying feature. So PipeCD will provide a way to allow users to customize the trigger logic to fit with their situation. It will be something like: apiVersion: pipecd.dev/v1beta1
kind: Terraform
spec:
...
trigger:
# trigger a new deployment when any resource is out-of-sync.
onOutOfSync:
disable: true # default is `true`
# trigger a new deployment when received a command from web-console, pipectl or api
onCommand:
disable: false # default is `false`
# trigger a new deployment when the newly merged commits touch any resources of an application.
onCommit:
disable: false # default is `false`
Yes, Piped agent is a stateless component. A Piped agent can be installed in the Kubernetes cluster as a single pod (to deploy Kubernetes applications running inside that cluster), run as an AWS Fargate service, run as a CloudRun service, or run inside any machine. (Installation guides) Thanks. |
Beta Was this translation helpful? Give feedback.
Hi, @lloydchang
Firstly, thank you for your question. ❤️
Yes, I think that PipeCD conforms to those GitOps Principles.