# Agent Service Type

{% hint style="info" %}
This is an older version of the document. To view the most recent version of the document, click [here](https://docs.opsmx.com/products/opsmx-intelligent-software-delivery-platform/system-setup/opsmx-agent/service-type).
{% endhint %}

The Agent supports many services types generally, but the ones shown below are also supported by ISD and Spinnaker.

### Jenkins

Authentication types:  none, basic, bearer.<br>

Example configuration:<br>

```
services:
      - name: dev jenkins
        type: jenkins
        enabled: true
        config:
          url: https://dev.jenkins.example.com:8080
          credentials:
            type: bearer
            secretName: dev-jenkins-secret
```

### **Artifactory**

Authentication types:  none, basic, bearer.\
Example configuration:

```
services:
      - name: artifactory1
        type: artifactory
        enabled: true
        config:
          url: https://artifactory.example.com
          credentials:
            type: basic
            secretName: artifactory1-secret
```

### Kubernetes

The agent has the ability to manage any namespace in the Kubernetes cluster it is installed into.  However, it is disabled by default.<br>

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.<br>

In all cases, access control is provided based on the Spinnaker configuration for RBAC.<br>

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.<br>

To advertise a single Kubernetes account "kubernetes1" which provides access to all namespaces:

```
  services:
      - name: kubernetes1
        type: kubernetes
        enabled: true
```

To advertise a multiple Kubernetes accounts, with specific namespaces and names::

```
services:
      - name: kubernetes1
      type: kubernetes
        enabled: true
        namespaces:
          - name: kubernetes1-ns-test
            namespaces:
              - test
          - name: kubernetes-ns-default
            namespaces:
              - default
              - test

```

When advertising multiple instances, the top-level name is ignored.<br>