Files
home-assistant-kubernetes/ci-deployer.yaml
T
feedc0de cd34e7413d
Validate and deploy Home Assistant / Validate manifests (push) Successful in 22s
Validate and deploy Home Assistant / Deploy to Kubernetes (push) Successful in 2m37s
Initial commit of my existing home-assistant config files and CI
2026-08-08 22:26:36 +02:00

80 lines
1.6 KiB
YAML

# Bootstrap this file once with an administrator identity. CI can update only
# the existing Home Assistant resources and cannot call the Secrets API.
apiVersion: v1
kind: ServiceAccount
metadata:
name: home-assistant-deployer
namespace: default
automountServiceAccountToken: false
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
name: home-assistant-deployer
namespace: default
rules:
- apiGroups:
- ""
resources:
- services
resourceNames:
- home-assistant
verbs:
- get
- patch
- update
- apiGroups:
- ""
resources:
- persistentvolumeclaims
resourceNames:
- home-assistant-pvc
verbs:
- get
- patch
- update
- apiGroups:
- apps
resources:
- deployments
resourceNames:
- home-assistant
verbs:
- get
- patch
- update
- apiGroups:
- networking.k8s.io
resources:
- ingresses
resourceNames:
- home-assistant
- home-assistant-auth
verbs:
- get
- patch
- update
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: home-assistant-deployer
namespace: default
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: home-assistant-deployer
subjects:
- kind: ServiceAccount
name: home-assistant-deployer
namespace: default
---
apiVersion: v1
kind: Secret
metadata:
name: home-assistant-deployer-token
namespace: default
annotations:
kubernetes.io/service-account.name: home-assistant-deployer
type: kubernetes.io/service-account-token