Giter Site home page Giter Site logo

provider-zpa's Introduction

provider-zpa

Crossplane provider for [Zscaler ZPA] The provider built from this repository can be installed into a Crossplane control plane or run seperately. It provides the following features:

  • Extension of the K8s API with CRDs to represent zscaler zpa objects as K8s resources
  • Controllers to provision these resources into a zscaler zpa instance
  • Implementations of Crossplane's portable resource abstractions, enabling zscaler zpa resources to fulfill a user's general need for cloud services

Getting Started and Documentation

For getting start with Crossplane setup installation and deployment, see the official documentation.

To use provider-zpa

  1. Create a new Zscaler ZPA ClientID and ClientSecret, and store it in a K8s secret
  2. Create a new ProviderConfig resource with a references to this secret

You are now ready to create resources as described in examples.

Contributing

provider-zpa is a community driven project and we welcome contributions. See the Crossplane Contributing guidelines to get started.

Adding New Resource

New resources can be added by defining the required types in apis and the controllers pkg/controllers/.

To generate the CRD YAML files run

make generate

Report a Bug

For filing bugs, suggesting improvements, or requesting new features, please open an issue.

Contact

Please use the following to reach members of the community:

Governance and Owners

provider-zpa is run according to the same Governance and Ownership structure as the core Crossplane project.

Code of Conduct

provider-zpa adheres to the same Code of Conduct as the core Crossplane project.

Licensing

provider-zpa is under the Apache 2.0 license.

Usage

To run the project

make run

To run all tests:

make test

To build the project

make build

To list all available options

make help

See more

provider-zpa's People

Contributors

haarchri avatar maltejk avatar

Stargazers

 avatar Roberto Acevedo avatar William Guilherme avatar  avatar Steven Klar avatar Hasan Turken avatar Daniel Mangum avatar Maximilian Ehlers avatar

Watchers

 avatar William Guilherme avatar  avatar

Forkers

haarchri maltejk

provider-zpa's Issues

release 0.4.0

Checklist

  • Create the new release branch with minor version, i.e. release-0.21 for v0.21.0.
    • You can use the existing branch for patch releases.
  • Tag release by running Tag action in Github UI against release branch, i.e. release-X branch.
    • Use v-prefixed version, like v0.21.0, for both description and tag.
  • Run CI action against release branch.
  • Tag the next pre-release by running Tag action in Github UI against master branch, if it's not a patch release.
    • The tag should be v0.22.0-rc.0 if you're releasing v0.21.x.
  • Validate that you can install the published version, basic sanity check.
  • Run Promote action to promote it in alpha channel if it's pre-1.0.
  • Use Github UI to generate release notes.
    • Make sure to scan all PRs marked with breaking-change and add instructions for users to handle them.
  • Create the next release issue with a title that has its date, 4 weeks after the current release day.
  • Announce in Slack, Twitter etc.

Release v0.3.0 on Sep. 07, 2022

Checklist

  • Create the new release branch with minor version, i.e. release-0.21 for v0.21.0.
    • You can use the existing branch for patch releases.
  • Tag release by running Tag action in Github UI against release branch, i.e. release-X branch.
    • Use v-prefixed version, like v0.21.0, for both description and tag.
  • Run CI action against release branch.
  • Tag the next pre-release by running Tag action in Github UI against master branch, if it's not a patch release.
    • The tag should be v0.22.0-rc.0 if you're releasing v0.21.x.
  • Validate that you can install the published version, basic sanity check.
  • Run Promote action to promote it in alpha channel if it's pre-1.0.
  • Use Github UI to generate release notes.
    • Make sure to scan all PRs marked with breaking-change and add instructions for users to handle them.
  • Create the next release issue with a title that has its date, 4 weeks after the current release day.
  • Announce in Slack, Twitter etc.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.