Line up default config
- create the namespace that's part of the kustomization - get names right in the patches - don't use a name prefix, it just confuses things
This commit is contained in:
parent
7931c12aa2
commit
ddf988b974
|
|
@ -1,13 +1,6 @@
|
|||
# Adds namespace to all resources.
|
||||
namespace: image-automation-system
|
||||
|
||||
# Value of this field is prepended to the
|
||||
# names of all resources, e.g. a deployment named
|
||||
# "wordpress" becomes "alices-wordpress".
|
||||
# Note that it should also match with the prefix (text before '-') of the namespace
|
||||
# field above.
|
||||
namePrefix: image-automation-
|
||||
|
||||
# Labels to add to all resources and selectors.
|
||||
#commonLabels:
|
||||
# someName: someValue
|
||||
|
|
@ -24,6 +17,9 @@ bases:
|
|||
# [PROMETHEUS] To enable prometheus monitor, uncomment all sections with 'PROMETHEUS'.
|
||||
#- ../prometheus
|
||||
|
||||
resources:
|
||||
- namespace.yaml
|
||||
|
||||
patchesStrategicMerge:
|
||||
# Protect the /metrics endpoint by putting it behind auth.
|
||||
# If you want your controller-manager to expose the /metrics
|
||||
|
|
|
|||
|
|
@ -3,8 +3,8 @@
|
|||
apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
metadata:
|
||||
name: controller-manager
|
||||
namespace: system
|
||||
name: image-automation-controller
|
||||
namespace: image-automation-system
|
||||
spec:
|
||||
template:
|
||||
spec:
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
apiVersion: apps/v1
|
||||
kind: Deployment
|
||||
metadata:
|
||||
name: controller-manager
|
||||
namespace: system
|
||||
name: image-automation-controller
|
||||
namespace: image-automation-system
|
||||
spec:
|
||||
template:
|
||||
spec:
|
||||
|
|
|
|||
|
|
@ -0,0 +1,6 @@
|
|||
apiVersion: v1
|
||||
kind: Namespace
|
||||
metadata:
|
||||
name: image-automation-system
|
||||
labels:
|
||||
control-plane: controller-manager
|
||||
Loading…
Reference in New Issue