Skip to content

Commit 23b1e07

Browse files
authored
Merge branch 'main' into kubevirt-csi-driver
2 parents 60e3b64 + 3b345d2 commit 23b1e07

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

72 files changed

+7930
-1
lines changed

packs/cloudcasa-3.1.0/README.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# CloudCasa Kubernetes Agent
2+
3+
[CloudCasa](https://cloudcasa.io) - Leader in Kubernetes Data Protection and Application Mobility
4+
5+
CloudCasa is a SaaS data protection, disaster recovery, migration, and replication solution for Kubernetes and cloud-native applications.
6+
Configuration is quick and easy, and basic service is free.
7+
8+
This pack installs and configures the CloudCasa agent on a Kubernetes cluster.
9+
10+
## Prerequisites
11+
12+
- Kubernetes 1.20 or above
13+
- A CloudCasa account. You can [sign up](https://signup.cloudcasa.io/) for free.
14+
- A CloudCasa **Cluster ID** (see below)
15+
16+
## Parameters
17+
18+
To deploy the CloudCasa agent, you **must** set the `clusterID` parameter to the Cluster ID provided by CloudCasa.
19+
All other parameters are optional or can be left at their default values.
20+
21+
| Key | Type | Default | Required |
22+
|--- |--- |--- |--- |
23+
| clusterID | string | `""` | Yes |
24+
| image.repository | string | `"docker.io/catalogicsoftware/amds-kagent"` | Yes |
25+
| image.tag | string | `"3.1.0-prod"` | Yes |
26+
| imagePullSecret | string | `null` | No |
27+
28+
## Usage
29+
30+
1. Log in to https://home.cloudcasa.io and add your Kubernetes cluster under Clusters/Overview. Note the returned cluster ID.
31+
2. Install the pack, setting the `clusterID` parameter to the returned ID.
32+
33+
This will install the CloudCasa agent and complete registration of the cluster with the CloudCasa service.
34+
35+
### Using an alternate image repository
36+
37+
The agent manager container can be installed from an alternate repository by setting values for image.repository and image.tag.
38+
Note that the alternate repository will also need to be set for the cluster in CloudCasa so that all agent containers will be loaded from it.
39+
See the [CloudCasa User Guide](https://docs.cloudcasa.io/help/cluster-add.html) for more information.
40+
41+
If the registry you are using requires authentication, you can define a Kubernetes secret with the authentication information
42+
and reference it by setting a value for imagePullSecret.
43+
See the [Kubernetes Docs](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/) for more information.
44+
Note that the secret name will also need to be set for the cluster in CloudCasa so that it will be used for all agent containers.
45+
See the [CloudCasa User Guide](https://docs.cloudcasa.io/help/cluster-add.html) for more information.
46+
47+
## References
48+
49+
- The CloudCasa Website: [https://cloudcasa.io](https://cloudcasa.io/)
50+
- The CloudCasa [User Guide](https://docs.cloudcasa.io/help/)
51+
- The CloudCasa [Getting Started Guide](https://cloudcasa.io/get-started)
52+
53+
*CloudCasa is a trademark of Catalogic Software, Inc.*
3.63 KB
Binary file not shown.

packs/cloudcasa-3.1.0/logo.png

21.2 KB
Loading

packs/cloudcasa-3.1.0/pack.json

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
{
2+
"name": "cloudcasa",
3+
"version": "3.1.0",
4+
"displayName": "CloudCasa Kubernetes Agent",
5+
"annotations": {
6+
"source": "community",
7+
"contributor" : "catalogic"
8+
},
9+
"layer": "addon",
10+
"addonType": "system app",
11+
"cloudTypes": [ "all" ],
12+
"charts": [ "charts/cloudcasa-3.4.4.tgz" ]
13+
}

packs/cloudcasa-3.1.0/values.yaml

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
pack:
2+
# The namespace (on the target cluster) in which the pack will be deployed.
3+
# When the namespace is not found, a new namespace will be created with the name specified.
4+
# Note this namespace MUST NOT BE CHANGED from "cloudcasa-io".
5+
namespace: "cloudcasa-io"
6+
content:
7+
images:
8+
- image: docker.io/catalogicsoftware/amds-kagent:3.1.0-prod
9+
10+
charts:
11+
cloudcasa:
12+
# clusterID is the CloudCasa Cluster ID. To be provided by the user.
13+
clusterID: ""
14+
15+
# image is the container repository and tag for the agent manager
16+
image:
17+
repository: "docker.io/catalogicsoftware/amds-kagent"
18+
tag: "3.1.0-prod"
19+
20+
# imagePullSecret is the name of the secret to use for image registry credentials (optional)
21+
imagePullSecret:

packs/crossplane-1.19.1/README.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
# Crossplane
2+
3+
Crossplane is an open source Kubernetes extension that transforms your Kubernetes cluster into a universal control plane.
4+
5+
Crossplane lets you manage anything, anywhere, all through standard Kubernetes APIs. Crossplane can even let you order a pizza directly from Kubernetes. If it has an API, Crossplane can connect to it.
6+
7+
With Crossplane, platform teams can create new abstractions and custom APIs with the full power of Kubernetes policies, namespaces, role based access controls and more. Crossplane brings all your non-Kubernetes resources under one roof.
8+
9+
Custom APIs, created by platform teams, allow security and compliance enforcement across resources or clouds, without exposing any complexity to the developers. A single API call can create multiple resources, in multiple clouds and use Kubernetes as the control plane for everything.
10+
11+
## Prerequisites
12+
13+
Kubernetes >= 1.27.0
14+
15+
## Usage
16+
17+
Installing a provider creates new Kubernetes resources representing the Provider’s APIs. Installing a provider also creates a Provider pod that’s responsible for reconciling the Provider’s APIs into the Kubernetes cluster. Providers constantly watch the state of the desired managed resources and create any external resources that are missing.
18+
19+
Install a Provider with a Crossplane Provider object setting the spec.package value to the location of the provider package. Additional providers can be found in the [Upboud Marketplace](https://marketplace.upbound.io/)
20+
21+
*For Example*
22+
Install the [Palette Provider](https://marketplace.upbound.io/providers/crossplane-contrib/provider-palette/v0.19.2)
23+
24+
```yaml
25+
apiVersion: pkg.crossplane.io/v1
26+
kind: Provider
27+
metadata:
28+
name: provider-palette
29+
spec:
30+
package: xpkg.upbound.io/crossplane-contrib/provider-palette:v0.23.5
31+
```
32+
33+
## References
34+
35+
Crossplane Provider Guide - <https://docs.crossplane.io/latest/concepts/providers/>
36+
Crossplane Concepts - <https://docs.crossplane.io/latest/concepts/>
37+
Upbound Marketplace - <https://marketplace.upbound.io/>
14.1 KB
Binary file not shown.

packs/crossplane-1.19.1/logo.png

89 KB
Loading

packs/crossplane-1.19.1/pack.json

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
{
2+
"addonType": "system app",
3+
"annotations": {
4+
"source": "community",
5+
"contributor" : "spectrocloud"
6+
},
7+
"cloudTypes": [
8+
"all"
9+
],
10+
"displayName": "Crossplane",
11+
"charts": [
12+
"charts/crossplane-1.19.1.tgz"
13+
],
14+
"layer":"addon",
15+
"name": "crossplane",
16+
"version": "1.19.1"
17+
}
18+
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
presets:
2+
- name: "palette-provider"
3+
displayName: "Enable Spectro Cloud Palette Provider"
4+
group: "Provider"
5+
remove: []
6+
add: |
7+
charts:
8+
crossplane:
9+
provider:
10+
packages:
11+
- "xpkg.upbound.io/crossplane-contrib/provider-palette:v0.23.5"

0 commit comments

Comments
 (0)