User Guide
Search…
Guides
Fundamentals
Setting up Ecosystem Integrations
What integrations are available
Integrate and Orchestrate your CI/CD toolchain with Ozone
The basics
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 source provider and a cloud provider with permissions to deploy to clusters through a registry.
Integrations
- 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
Creating a provider
Go to the Setup section and click on a provider. The permissions that we require on the tokens are explained to you through the setup process.
Example: A GCP Cloud Provider Integration
Last modified 4mo ago
Copy link