Skip to content

Commit

Permalink
Readme updates (#15)
Browse files Browse the repository at this point in the history
* Update README.md

* description & README

* Update README.md

* Update README.md
  • Loading branch information
tr0njavolta authored Feb 7, 2024
1 parent ef0c106 commit 1b25380
Show file tree
Hide file tree
Showing 2 changed files with 44 additions and 2 deletions.
40 changes: 38 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,39 @@
# configuration-gcp-gke
# GCP GKE Configuration

GCP GKE Configuration is reusable Configuration designed to be primarily used in higher level Configurations.

This repository contains a [Crossplane configuration](https://docs.crossplane.io/latest/concepts/packages/#configuration-packages), tailored for users establishing their initial control plane with [Upbound](https://cloud.upbound.io). This configuration deploys fully managed GCP GKE instances.

## Overview

The core components of a custom API in [Crossplane](https://docs.crossplane.io/latest/getting-started/introduction/) include:

- **CompositeResourceDefinition (XRD):** Defines the API's structure.
- **Composition(s):** Implements the API by orchestrating a set of Crossplane managed resources.

In this specific configuration, the GCP GKE API contains:

- **a [GCP GKE](/apis/definition.yaml) custom resource type.**
- **Composition of the GCP GKE resources:** Configured in [/apis/composition.yaml](/apis/composition.yaml), it provisions an GCP GKEand resources in the `upbound-system` namespace.

This repository contains an Composite Resource (XR) file.

## Deployment

```shell
apiVersion: pkg.crossplane.io/v1
kind: Configuration
metadata:
name: configuration-gcp-network
spec:
package: xpkg.upbound.io/upbound/configuration-gcp-network:v0.1.0
```

## Next steps

This repository serves as a foundational step. To enhance your control plane, consider:

1. create new API definitions in this same repo
2. editing the existing API definition to your needs


Upbound will automatically detect the commits you make in your repo and build the configuration package for you. To learn more about how to build APIs for your managed control planes in Upbound, read the guide on Upbound's docs.
6 changes: 6 additions & 0 deletions crossplane.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,12 @@ metadata:
meta.crossplane.io/maintainer: Upbound <[email protected]>
meta.crossplane.io/source: github.com/upbound/configuration-gcp-gke
meta.crossplane.io/license: Apache-2.0
meta.crossplane.io/description: |
This configuration provides a foundation to build and operate GCP GKE.
meta.crossplane.io/readme: |
This configuration is used for deploying and managing GCP GKE clusters on Kubernetes using Crossplane. This setup provides the necessary infrastructure to deploy GCP GKE resources managed with Crossplane in Kubernetes. This approach ensures a flexible, streamlined deployment workflow.
For more details and customization options, you can explore [the GitHub repository](https://github.com/upbound/configuration-app).
spec:
crossplane:
version: ">=v1.14.1-0"
Expand Down

0 comments on commit 1b25380

Please sign in to comment.