The agent supports many services types generally, but the ones shown below are also supported by OES and Spinnaker.
Authentication types: none, basic, bearer.
services:- name: dev jenkinstype: jenkinsenabled: trueconfig:url: https://dev.jenkins.example.com:8080credentials:type: bearersecretName: dev-jenkins-secret
Authentication types: none, basic, bearer. Example configuration:
services:- name: artifactory1type: artifactoryenabled: trueconfig:url: https://artifactory.example.comcredentials:type: basicsecretName: artifactory1-secret
The agent has the ability to manage any namespace in the Kubernetes cluster it is installed into. However, it is disabled by default.
The Kubernetes service can be configured in two ways: a single Kubernetes account is advertised to Spinnaker, or multiple accounts with the same credentials advertised to Spinnaker, with different namespaces.
In all cases, access control is provided based on the Spinnaker configuration for RBAC.
Multiple clusters are not supported at this time, but multiple agents can be used, one per cluster. The namespace restrictions in the following examples are views into a single cluster, the one where the agent is running.
To advertise a single Kubernetes account "kubernetes1" which provides access to all namespaces:
services:- name: kubernetes1type: kubernetesenabled: true
To advertise a multiple Kubernetes accounts, with specific namespaces and names::
services:- name: kubernetes1type: kubernetesenabled: truenamespaces:- name: kubernetes1-ns-testnamespaces:- test- name: kubernetes-ns-defaultnamespaces:- default- test
When advertising multiple instances, the top-level name is ignored.