Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write public cloud docs for major cloud providers #220

Closed
3 tasks done
caseydavenport opened this issue Nov 15, 2016 · 1 comment
Closed
3 tasks done

Write public cloud docs for major cloud providers #220

caseydavenport opened this issue Nov 15, 2016 · 1 comment

Comments

@caseydavenport
Copy link
Member

caseydavenport commented Nov 15, 2016

We need docs in this section: http://docs.projectcalico.org/v2.0/reference/public-cloud/overview

This issue covers docs for:

We've already got this information floating around in various other guides. We should be removing it from all of those places and keeping a "Calico on AWS", "Calico on GCE", etc style doc for each provider.

@ozdanborne
Copy link
Member

#315 and #321 were closed, but might provide a useful base for resolving this.

@ozdanborne ozdanborne removed their assignment Jan 30, 2017
@caseydavenport caseydavenport removed this from the Calico v2.1.0 milestone Jan 30, 2017
@robbrockbank robbrockbank added this to the Calico v2.6.0 milestone Aug 8, 2017
@bcreane bcreane removed this from the Calico v2.6.0 milestone Sep 21, 2017
tomdee pushed a commit that referenced this issue Mar 6, 2018
caseydavenport pushed a commit that referenced this issue Dec 14, 2021
…upstream-release-v3.20

Automated cherry pick of #220: Change release repo to docker.io, add RELEASE and CONFIRM env
brandonrjacobs pushed a commit to coreweave/calico that referenced this issue Jan 11, 2024
…3.6-auto-libcalico-update

[release-v3.6] Automatic patch of libcalico-go to 24a5a971c54bf0f43417bbfccd0b31e7ffa19a98
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants