Closed jamengual closed 1 day ago
+1
This will be long-winded, but I'm posting here due to the issue's high visibility.
This project is a weird candidate for CNCF, because it is not inherently cloud-native. It can be used in a cloud-native way, but it can also be used in the complete absence of Kubernetes, containers, or microservices.
This proposal hinges on the question of: does CNCF want to increase its scope to cover configuration management and deployment? If the CDF still existed, we might suggest it as an alternate foundation, but that's not an option anymore.
Josh does have a point on Atlantis not entirely fitting the CNCF as it currently stands. I've been attending multiple talks and meetings at KubeCon EU to try and figure out the answer to this and to see how we can be part of the solution and not the problem. Atlantis isn't the only project residing in this "grey" area, and there's a need to figure out where projects of this scope fit into the ecosystem and if the CNCF is willing to expand their scope to include them.
There are also contributing factors from the CNCF side that exacerbate this. They do not have enough contributors participating in the TAGs (Technical Advisory Groups), which results in TAGs being overloaded with expanding scope. I highly encourage everyone to please join a TAG in your area of interest and contribute. You can find a list of TAGs here: https://github.com/cncf/toc/tree/main/tags
After the App-Delivery maintainer track talk at KubeCon and discussions with the TAG chairs, I'm happy to announce that I have volunteered to help coordinate and evaluate the building of a new working group around "Infrastructure Provisioning" within the App-Delivery TAG (https://github.com/cncf/tag-app-delivery/issues/589). To start, I will reach out to coordinate with similar projects, such as OpenTofu and Crossplane.
If you wish to support/provide feedback, please consider joining the bi-monthly TAG meetings and Slack, which can be found here: https://tag-app-delivery.cncf.io/. Otherwise, a simple +1 is a great way to show your support and that we're thinking in the right direction. Thank you
I've been discussing a related topic with @angellk, and to @GenPage's point, Atlantis isn't the only project facing issues. Other initiatives like "hosted control planes" have also been caught in the grey area. While we could opt for runtime, I haven't found a suitable tag/wg for topics like infrastructure, multi-cluster management, control-planes, and lifecycle.
@GenPage I am happy to collaborate (others in the hcp space are willing as well) to determine the right place for those efforts. I believe it would make sense to create a new WG that covers infra, multi-cluster management, control planes, and lifecycle projects, which would include cross-plane and open tofu as well. We could work on the naming to make sure the scope covers those efforts as well.
+1
+1 , and you now having me look at the App Delivery TAG.
+1
+1
+1
+1
+1
+1
Then half of CNCF projects are weird candidates for CNCF, including graduated projects such as Prometheus, Fluentd or even Cilium because those can be used without containers, Kubernetes and microservices
They can be but materially they are not. It's unquestionable that the primary, 95% use case of Prometheus is collecting metrics for Kubernetes-based stacks. Most Cillium users are on top of a Kubernetes distribution. Etc. If you're making the case that Atlantis is used primarily for building cloud native stacks, rather than for other configuration management tasks, then that's a good case to make for this application. Are you?
+1
Then half of CNCF projects are weird candidates for CNCF, including graduated projects such as Prometheus, Fluentd or even Cilium because those can be used without containers, Kubernetes and microservices
They can be but materially they are not. It's unquestionable that the primary, 95% use case of Prometheus is collecting metrics for Kubernetes-based stacks. Most Cillium users are on top of a Kubernetes distribution. Etc. If you're making the case that Atlantis is used primarily for building cloud native stacks, rather than for other configuration management tasks, then that's a good case to make for this application. Are you?
Most Atlantis users use Atlantis in Kubernetes, bootstrapping other Kubernetes clusters using Atlantis, and deploying their apps in Kubernetes using Atlantis workflows.
Then half of CNCF projects are weird candidates for CNCF, including graduated projects such as Prometheus, Fluentd or even Cilium because those can be used without containers, Kubernetes and microservices
They can be but materially they are not. It's unquestionable that the primary, 95% use case of Prometheus is collecting metrics for Kubernetes-based stacks. Most Cillium users are on top of a Kubernetes distribution. Etc. If you're making the case that Atlantis is used primarily for building cloud native stacks, rather than for other configuration management tasks, then that's a good case to make for this application. Are you?
I think the vast majority of use cases for Atlantis is to be collaboration tool for a cloud infrastructure orchestration, but of course it can be used for something else
+1
+1
+1
Most Atlantis users use Atlantis in Kubernetes, bootstrapping other Kubernetes clusters using Atlantis, and deploying their apps in Kubernetes using Atlantis workflows.
Great! Please add that to your original application text, in case members of the TOC aren't reading the whole comment thread. It can go in either Cloud Native Integration or Cloud Native Fit.
TAG-CS Comment:
Atlantis currently has:
They do not have other project internal documentation ... yet.
Follow-up from today's sandbox review, Atlantis will be moved to a vote. Just for an FYI though - you may be requested to change the name pending trademark review. /vote
@mrbobbytables has called for a vote on [Sandbox] Atlantis
(#60).
The members of the following teams have binding votes: | Team |
---|---|
@cncf/cncf-toc |
Non-binding votes are also appreciated as a sign of support!
You can cast your vote by reacting to this
comment. The following reactions are supported:
In favor | Against | Abstain |
---|---|---|
π | π | π |
Please note that voting for multiple options is not allowed and those votes won't be counted.
The vote will be open for 2months 30days 2h 52m 48s
. It will pass if at least 66%
of the users with binding votes vote In favor π
. Once it's closed, results will be published here as a new comment.
So far 9.09%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
1 | 0 | 0 | 10 |
User | Vote | Timestamp |
---|---|---|
dims | In favor | 2024-06-11 23:04:45.0 +00:00:00 |
@rochaporto | Pending | |
@angellk | Pending | |
@mauilion | Pending | |
@linsun | Pending | |
@dzolotusky | Pending | |
@kevin-wangzefeng | Pending | |
@cathyhongzhang | Pending | |
@nikhita | Pending | |
@TheFoxAtWork | Pending | |
@kgamanji | Pending |
/check-vote
So far 45.45%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
5 | 0 | 0 | 6 |
User | Vote | Timestamp |
---|---|---|
TheFoxAtWork | In favor | 2024-06-12 20:33:29.0 +00:00:00 |
rochaporto | In favor | 2024-06-12 9:11:03.0 +00:00:00 |
dims | In favor | 2024-06-11 23:04:45.0 +00:00:00 |
nikhita | In favor | 2024-06-14 5:49:12.0 +00:00:00 |
angellk | In favor | 2024-06-12 16:45:14.0 +00:00:00 |
@mauilion | Pending | |
@linsun | Pending | |
@dzolotusky | Pending | |
@kevin-wangzefeng | Pending | |
@cathyhongzhang | Pending | |
@kgamanji | Pending |
+1
/check-vote
So far 54.55%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
6 | 0 | 0 | 5 |
User | Vote | Timestamp |
---|---|---|
TheFoxAtWork | In favor | 2024-06-12 20:33:29.0 +00:00:00 |
nikhita | In favor | 2024-06-14 5:49:12.0 +00:00:00 |
rochaporto | In favor | 2024-06-12 9:11:03.0 +00:00:00 |
angellk | In favor | 2024-06-12 16:45:14.0 +00:00:00 |
cathyhongzhang | In favor | 2024-06-14 15:51:55.0 +00:00:00 |
dims | In favor | 2024-06-11 23:04:45.0 +00:00:00 |
@mauilion | Pending | |
@linsun | Pending | |
@dzolotusky | Pending | |
@kevin-wangzefeng | Pending | |
@kgamanji | Pending |
/check-vote
Votes can only be checked once a day.
The vote passed! π
81.82%
of the users with binding vote were in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
9 | 0 | 0 | 2 |
User | Vote | Timestamp |
---|---|---|
@dims | In favor | 2024-06-11 23:04:45.0 +00:00:00 |
@cathyhongzhang | In favor | 2024-06-14 15:51:55.0 +00:00:00 |
@TheFoxAtWork | In favor | 2024-06-12 20:33:29.0 +00:00:00 |
@kevin-wangzefeng | In favor | 2024-06-18 2:02:32.0 +00:00:00 |
@kgamanji | In favor | 2024-06-18 6:37:43.0 +00:00:00 |
@nikhita | In favor | 2024-06-14 5:49:12.0 +00:00:00 |
@dzolotusky | In favor | 2024-06-18 4:09:12.0 +00:00:00 |
@rochaporto | In favor | 2024-06-12 9:11:03.0 +00:00:00 |
@angellk | In favor | 2024-06-12 16:45:14.0 +00:00:00 |
This is exciting!! π― Thanks everyone for helping us move forward. π
I eco @chenrui333, thanks again for the support and please keep guiding us through the process.
This is the start of an exciting long journey with the project.
Big supporter of Atlantis, have been using the product, and want it to go forward and big!
Hello and congrats on being accepted as a CNCF Sandbox project!
Here is the link to your onboarding task list: https://github.com/cncf/toc/issues/1369
Feel free to reach out with any questions you might have!
Application contact emails
jose.amengual@gmail.com dylandcpage@gmail.com rui@chenrui.dev
Project Summary
Terraform Pull Request Automation
Project Description
Atlantis is PR automation application that allows users to create PRs against a repository to run terraform via command comments like
atlantis plan/apply/import/unlock
. It allows users to interact with terraform commands within the PR and get the output of those commands in the form of PR comments. Users can define project structures, generate policies, autogenerate projects, require review requirements etc. Atlantis supports multiples VCSs Github, Gitlab, BitBucket, Azure PipelinesOrg repo URL (provide if all repos under the org are in scope of the application)
https://github.com/runatlantis
Project repo URL in scope of application
https://github.com/runatlantis/atlantis
Additional repos in scope of the application
No response
Website URL
https://www.runatlantis.io/
Roadmap
https://github.com/runatlantis/atlantis/milestones
Roadmap context
No response
Contributing Guide
https://github.com/runatlantis/atlantis/blob/main/CONTRIBUTING.md
Code of Conduct (CoC)
https://github.com/runatlantis/atlantis/blob/main/CODE_OF_CONDUCT.md
Adopters
https://github.com/runatlantis/atlantis/issues/2626
Contributing or Sponsoring Org
No response
Maintainers file
https://github.com/runatlantis/atlantis/blob/main/MAINTAINERS.md
IP Policy
Trademark and accounts
Why CNCF?
Atlantis has been part of the IaC community for many many years and lately, after a few years dormant it has been reviving thanks to the work of the maintainers and the community, it is more than ever vitally crucial for many companies and individuals these days were there is more and more IaC adoption in the industry. But without a good supporting structure, Atlantis could potentially one day go dormant forever and it will fracture the long-lasting community that it has built. That is why we believe by donating the project to the CNCF we could get the much-needed supporting structure to the project and drive a richer contributor community.
Benefit to the Landscape
As I said before, the project has been a long-time key player in the community, and its role in IaC and cloud infrastructure is vital, we feel that CNCF is a natural fit for the project. Many CNCF projects actually run Atlantis to create their own infrastructure to actually deploy their own code to the cloud resources or to deploy other CNCF projects in their infrastructure. It is a key piece withing the cloud native infrastructure.
Cloud Native 'Fit'
The Atlantis project fits within the Automation/Configuration section on the CNCF alongside terraform, ArgoCD, and others. It uses the GitOps workflow to run terraform automation to then deploy resources to support different other types of applications like, Kubernetes, Argo and many others. It sits in a key part of the deployment workflow of many cloud native application.
Most Atlantis users use Atlantis in Kubernetes, bootstrapping other Kubernetes clusters using Atlantis, and deploying their apps in Kubernetes using Atlantis workflows.
Cloud Native 'Integration'
Atlantis runs primarily Terraform project in a GitOps workflow. Any Terrafrom project can be run through atlantis and be enhanced by the many features that it offers. Atlantis complements terraform in particular by moving the IaC to the left, closer to the developer so that the interaction with terraform happens in familiar tools to the developer.
Cloud Native Overlap
none I believe
Similar projects
ArgoCD
Landscape
I do not think we are listed
Business Product or Service to Project separation
N/A
Project presentations
N/A
Project champions
N/A
Additional information
The project owner has authorized us to submit the project and has made us the official maintainers.
https://github.com/runatlantis/atlantis/issues/3686