Skip to content

docs: add guide for template ImagePullSecret #11608

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

Merged
merged 3 commits into from
Jan 13, 2024
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
add: manifest
  • Loading branch information
ericpaulsen committed Jan 13, 2024
commit c126eb1347da838b856334f1f63d0aad00460c8f
4 changes: 2 additions & 2 deletions docs/guides/image-pull-secret.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,8 @@ January 12, 2024

Coder workspaces are commonly run as Kubernetes pods. When run inside of an enterprise,
the pod image is typically pulled from a private image registry. This guide walks
through creating an ImagePullSecret to use for authenticating to your registry.
through creating an ImagePullSecret to use for authenticating to your registry,
and defining it in your workspace template.

## 1. Create Docker Config JSON File

Expand Down Expand Up @@ -75,4 +76,3 @@ resource "kubernetes_pod" "dev" {
}
}
```

5 changes: 5 additions & 0 deletions docs/manifest.json
Original file line number Diff line number Diff line change
Expand Up @@ -1020,6 +1020,11 @@
"title": "Google to AWS Federation",
"description": "Federating a Google Cloud service account to AWS",
"path": "./guides/gcp-to-aws.md"
},
{
"title": "Template ImagePullSecrets",
"description": "Creating ImagePullSecrets for private registries",
"path": "./guides/image-pull-secret.md"
}
]
}
Expand Down