Setting up Ecosystem Integrations
Setup API integrations as a provider on Ozone. This lets Ozone orchestrate your CI/CD toolchain.
In Ozone, ecosystems integrations are abstracted by providers. We supply native integrations across the DevOps ecosystem wherein we typically accept something on the lines of a key for a Service Account or an API Token and store it securely into Ozone's Vault.
These provider integrations can then be scoped into Projects across Ozone. For example, if you have a microservice that you would like to deploy to a cluster, you would need at the very least a git provider and a cloud provider with access to clusters through a registry.
.png?alt=media&token=f54e24b6-f213-449d-8173-f6428703560a)
- Cloud Providers:
- EKS, AKS, GKE, PKS, Tanzu, Openshift and any other CNCF compliant Kubernetes Distribution
- Source Code Providers:
- Github, Bitbucket and Gitlab
- Container Registries
- Cloud: ACR, GCR, ECR
- On-premise: JFrog, Harbor and Quay
- Notification Mechanisms
- Email
- In-App Notifications
- Issue Trackers
- JIRA
- Single Sign On
- GSuite, LDAP, Azure Active Directory
- Security
- Snyk, Sonarqube and Clair
- Private Catalogs
- Custom Tasks for Pipelines and Releases
- Private Helm Channels hosted on JFrog and Harbor
- Navigate to Resources on the sidebar
- Click on providers
- Click on create a new provider
- Select the provider integration of your choice
- Enter the credentials and test your integration
- Resources, if any are synced and appear under the resources tab