cert-manager/docs/deploy/rbac/deployment.yaml
jetstack-ci-bot 97ce5ca2b3
Merge pull request #329 from munnerz/default-cluster-namespace
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Set default cluster resource namespace to current pod namespace

**What this PR does / why we need it**:

Changes the default cluster resource namespace from kube-system to the current namespace of the cert-manager deployment.

**Which issue this PR fixes**: fixes #103 

**Release note**:
```release-note
Supporting resources for ClusterIssuer's (e.g. signing CA certificates, or ACME account private keys) will now be stored in the same namespace as cert-manager, instead of kube-system in previous versions. Action required: you will need to ensure to properly manually migrate these referenced resources across into the deployment namespace of cert-manager, else cert-manager may not be able to find account private keys or signing CA certificates.
```

/cc @mikebryant
2018-02-23 19:56:21 +00:00

46 lines
1.1 KiB
YAML

##---
# Source: cert-manager/templates/deployment.yaml
apiVersion: apps/v1beta1
kind: Deployment
metadata:
name: cert-manager
namespace: "cert-manager"
labels:
app: cert-manager
chart: cert-manager-0.2.2
release: cert-manager
heritage: Tiller
spec:
replicas: 1
template:
metadata:
labels:
app: cert-manager
release: cert-manager
spec:
serviceAccountName: cert-manager
containers:
- name: cert-manager
image: "quay.io/jetstack/cert-manager-controller:v0.2.3"
imagePullPolicy: IfNotPresent
args:
- --cluster-resource-namespace=$(POD_NAMESPACE)
env:
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
resources:
requests:
cpu: 10m
memory: 32Mi
- name: ingress-shim
image: "quay.io/jetstack/cert-manager-ingress-shim:v0.2.3"
imagePullPolicy: IfNotPresent
resources:
requests:
cpu: 10m
memory: 32Mi