Skip to content

Commit

Permalink
Merge branch 'main' into release-appdynamics-collectors-1.22.1287
Browse files Browse the repository at this point in the history
  • Loading branch information
vishwanaths authored Oct 19, 2024
2 parents 1ec9d74 + 17ab912 commit 84d3826
Show file tree
Hide file tree
Showing 28 changed files with 3,180 additions and 4 deletions.
37 changes: 37 additions & 0 deletions packs/crossplane-1.16/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
# Crossplane

Crossplane is an open source Kubernetes extension that transforms your Kubernetes cluster into a universal control plane.

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.

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.

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.

## Prerequisites

Kubernetes >= 1.27.0

## Usage

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.

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/)

*For Example*
Install the [Palette Provider](https://marketplace.upbound.io/providers/crossplane-contrib/provider-palette/v0.19.2)

```yaml
apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
name: provider-palette
spec:
package: xpkg.upbound.io/crossplane-contrib/provider-palette:v0.19.2
```
## References
Crossplane Provider Guide - <https://docs.crossplane.io/latest/concepts/providers/>
Crossplane Concepts - <https://docs.crossplane.io/latest/concepts/>
Upbound Marketplace - <https://marketplace.upbound.io/>
Binary file not shown.
Binary file added packs/crossplane-1.16/logo.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
18 changes: 18 additions & 0 deletions packs/crossplane-1.16/pack.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
{
"addonType": "system app",
"annotations": {
"source": "community",
"contributor" : "spectrocloud"
},
"cloudTypes": [
"all"
],
"displayName": "Crossplane",
"charts": [
"charts/crossplane-1.16.0.tgz"
],
"layer":"addon",
"name": "crossplane",
"version": "1.16.0"
}

11 changes: 11 additions & 0 deletions packs/crossplane-1.16/presets.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
presets:
- name: "palette-provider"
displayName: "Enable Spectro Cloud Palette Provider"
group: "Provider"
remove: []
add: |
charts:
crossplane:
provider:
packages:
- "xpkg.upbound.io/crossplane-contrib/provider-palette:v0.19.2"
197 changes: 197 additions & 0 deletions packs/crossplane-1.16/values.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,197 @@
pack:
#The namespace (on the target cluster) to install this chart
#When not found, a new namespace will be created
namespace: "crossplane-system"
content:
images:
- image: xpkg.upbound.io/crossplane/crossplane:v1.16.0


charts:
crossplane:
# helm-docs renders these comments into markdown. Use markdown formatting where
# appropiate.
#
# -- The number of Crossplane pod `replicas` to deploy.
replicas: 1

# -- The deployment strategy for the Crossplane and RBAC Manager pods.
deploymentStrategy: RollingUpdate

image:
# -- Repository for the Crossplane pod image.
repository: xpkg.upbound.io/crossplane/crossplane
# -- The Crossplane image tag. Defaults to the value of `appVersion` in `Chart.yaml`.
tag: ""
# -- The image pull policy used for Crossplane and RBAC Manager pods.
pullPolicy: IfNotPresent

# -- Add `nodeSelectors` to the Crossplane pod deployment.
nodeSelector: {}
# -- Add `tolerations` to the Crossplane pod deployment.
tolerations: []
# -- Add `affinities` to the Crossplane pod deployment.
affinity: {}

# -- Enable `hostNetwork` for the Crossplane deployment. Caution: enabling `hostNetwork` grants the Crossplane Pod access to the host network namespace. Consider setting `dnsPolicy` to `ClusterFirstWithHostNet`.
hostNetwork: false

# -- Specify the `dnsPolicy` to be used by the Crossplane pod.
dnsPolicy: ""

# -- Add custom `labels` to the Crossplane pod deployment.
customLabels: {}

# -- Add custom `annotations` to the Crossplane pod deployment.
customAnnotations: {}

serviceAccount:
# -- Add custom `annotations` to the Crossplane ServiceAccount.
customAnnotations: {}

# -- Enable [leader election](https://docs.crossplane.io/latest/concepts/pods/#leader-election) for the Crossplane pod.
leaderElection: true
# -- Add custom arguments to the Crossplane pod.
args: []

provider:
# -- A list of Provider packages to install.
packages: []

configuration:
# -- A list of Configuration packages to install.
packages: []

function:
# -- A list of Function packages to install
packages: []

# -- The imagePullSecret names to add to the Crossplane ServiceAccount.
imagePullSecrets: []

registryCaBundleConfig:
# -- The ConfigMap name containing a custom CA bundle to enable fetching packages from registries with unknown or untrusted certificates.
name: ""
# -- The ConfigMap key containing a custom CA bundle to enable fetching packages from registries with unknown or untrusted certificates.
key: ""

service:
# -- Configure annotations on the service object. Only enabled when webhooks.enabled = true
customAnnotations: {}

webhooks:
# -- Enable webhooks for Crossplane and installed Provider packages.
enabled: true

rbacManager:
# -- Deploy the RBAC Manager pod and its required roles.
deploy: true
# -- Don't install aggregated Crossplane ClusterRoles.
skipAggregatedClusterRoles: false
# -- The number of RBAC Manager pod `replicas` to deploy.
replicas: 1
# -- Enable [leader election](https://docs.crossplane.io/latest/concepts/pods/#leader-election) for the RBAC Manager pod.
leaderElection: true
# -- Add custom arguments to the RBAC Manager pod.
args: []
# -- Add `nodeSelectors` to the RBAC Manager pod deployment.
nodeSelector: {}
# -- Add `tolerations` to the RBAC Manager pod deployment.
tolerations: []
# -- Add `affinities` to the RBAC Manager pod deployment.
affinity: {}

# -- The PriorityClass name to apply to the Crossplane and RBAC Manager pods.
priorityClassName: ""

resourcesCrossplane:
limits:
# -- CPU resource limits for the Crossplane pod.
cpu: 500m
# -- Memory resource limits for the Crossplane pod.
memory: 1024Mi
requests:
# -- CPU resource requests for the Crossplane pod.
cpu: 100m
# -- Memory resource requests for the Crossplane pod.
memory: 256Mi

securityContextCrossplane:
# -- The user ID used by the Crossplane pod.
runAsUser: 65532
# -- The group ID used by the Crossplane pod.
runAsGroup: 65532
# -- Enable `allowPrivilegeEscalation` for the Crossplane pod.
allowPrivilegeEscalation: false
# -- Set the Crossplane pod root file system as read-only.
readOnlyRootFilesystem: true

packageCache:
# -- Set to `Memory` to hold the package cache in a RAM backed file system. Useful for Crossplane development.
medium: ""
# -- The size limit for the package cache. If medium is `Memory` the `sizeLimit` can't exceed Node memory.
sizeLimit: 20Mi
# -- The name of a PersistentVolumeClaim to use as the package cache. Disables the default package cache `emptyDir` Volume.
pvc: ""
# -- The name of a ConfigMap to use as the package cache. Disables the default package cache `emptyDir` Volume.
configMap: ""

resourcesRBACManager:
limits:
# -- CPU resource limits for the RBAC Manager pod.
cpu: 100m
# -- Memory resource limits for the RBAC Manager pod.
memory: 512Mi
requests:
# -- CPU resource requests for the RBAC Manager pod.
cpu: 100m
# -- Memory resource requests for the RBAC Manager pod.
memory: 256Mi

securityContextRBACManager:
# -- The user ID used by the RBAC Manager pod.
runAsUser: 65532
# -- The group ID used by the RBAC Manager pod.
runAsGroup: 65532
# -- Enable `allowPrivilegeEscalation` for the RBAC Manager pod.
allowPrivilegeEscalation: false
# -- Set the RBAC Manager pod root file system as read-only.
readOnlyRootFilesystem: true

metrics:
# -- Enable Prometheus path, port and scrape annotations and expose port 8080 for both the Crossplane and RBAC Manager pods.
enabled: false

# -- Add custom environmental variables to the Crossplane pod deployment.
# Replaces any `.` in a variable name with `_`. For example, `SAMPLE.KEY=value1` becomes `SAMPLE_KEY=value1`.
extraEnvVarsCrossplane: {}

# -- Add custom environmental variables to the RBAC Manager pod deployment.
# Replaces any `.` in a variable name with `_`. For example, `SAMPLE.KEY=value1` becomes `SAMPLE_KEY=value1`.
extraEnvVarsRBACManager: {}

# -- Add a custom `securityContext` to the Crossplane pod.
podSecurityContextCrossplane: {}

# -- Add a custom `securityContext` to the RBAC Manager pod.
podSecurityContextRBACManager: {}

# -- Add custom `volumes` to the Crossplane pod.
extraVolumesCrossplane: {}

# -- Add custom `volumeMounts` to the Crossplane pod.
extraVolumeMountsCrossplane: {}

# -- To add arbitrary Kubernetes Objects during a Helm Install
extraObjects: []
# - apiVersion: pkg.crossplane.io/v1alpha1
# kind: ControllerConfig
# metadata:
# name: aws-config
# annotations:
# eks.amazonaws.com/role-arn: arn:aws:iam::123456789101:role/example
# helm.sh/hook: post-install
# spec:
# podSecurityContext:
# fsGroup: 2000

1 change: 1 addition & 0 deletions packs/crossplane-1.7.0/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Crossplane Deprecated
3 changes: 2 additions & 1 deletion packs/crossplane-1.7.0/pack.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,8 @@
"addonType": "system app",
"annotations": {
"source": "community",
"contributor" : "spectrocloud"
"contributor" : "spectrocloud",
"system_state": "deprecated"
},
"cloudTypes": [
"all"
Expand Down
3 changes: 3 additions & 0 deletions packs/crossplane-1.7.0/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@ pack:
#The namespace (on the target cluster) to install this chart
#When not found, a new namespace will be created
namespace: "crossplane"
content:
images:
- image: xpkg.upbound.io/crossplane/crossplane:v1.7.0

charts:
crossplane:
Expand Down
31 changes: 30 additions & 1 deletion packs/csm-operator-addon-1.5.0/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,5 +17,34 @@ Please see [here](https://dell.github.io/csm-docs/docs/deployment/csmoperator/dr
# Cloud types supported:
This pack was designed to be used with clusters on Canonical MAAS

### Usage

Dell Container Storage Modules Operator is a Kubernetes native application which helps in installing and managing CSI Drivers and CSM Modules provided by Dell Technologies for its various storage platforms. Dell Container Storage Modules Operator uses Kubernetes CRDs (Custom Resource Definitions) to define a manifest that describes the deployment specifications for each driver to be deployed.

`StorageClass` are created and set as default. This creates the storageclass `vxflexos` for `powerflex-v2100`, `powermax` for `powermax-v2100` & `powerstore` for `powerstore-v2100`.


:::tip

Check out the [Palette Backup and Restore Documentation](https://docs.spectrocloud.com/clusters/cluster-management/backup-restore/) to learn how to backup and restore your cluster.

::::

### CSM Snapshot Controller Creation

The Dell Container Storage Modules Operator pack supports snapshot controller creation. After selecting the right `Platform` **preset**, modify the parameter `charts.csm-operator.snapshot-controller.enabled` to enable the controller snapshotter for `powerflex-v2100`, `powermax-v2100` & `powerstore-v2100`. Default value is `true`.

### CSM Volume Snapshot Creation

The Dell Container Storage Modules Operator pack supports creation of volume snapshots. After selecting the right `Platform` **preset**, modify the parameter `charts.csm-operator.snapshot-controller.volumeSnapshotClass.create` to enable the creation of `VolumeSnapshotClass` for `powerflex-v2100`, `powermax-v2100` & `powerstore-v2100`. By default, it is `true` for `powerflex-v2100` & `powerstore-v2100`. By default, it is `false` for `powermax-v2100`

### CSM Webhook Snapshot Creation

The Dell Container Storage Modules Operator pack supports snapshot volume creation. After selecting the right `Platform` **preset**, modify the parameter`charts.csm-operator.snapshot-controller.webhook.enable` to enable the snapshot webhook for `powerflex-v2100`, `powermax-v2100` & `powerstore-v2100`. By default it is `true` for `powerflex-v2100`, `powermax-v2100` & `powerstore-v2100`.


# References:
- https://github.com/dell/csm-operator

- [GITHUB](https://github.com/dell/csm-operator)

- [Palette Backup and Restore Documentation](https://docs.spectrocloud.com/clusters/cluster-management/backup-restore/)
2 changes: 1 addition & 1 deletion packs/hello-universe-1.1.2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ You can deploy it using two preset configurations:

- If you are using the **Enable Hello Universe API** preset, you will need the `:3000` port available on your cluster too. Check out the [Usage](#usage) section for further details.

- Ensure sufficient CPU resources within the cluster to allocate a minimum of 500 milliCPU and a maximum of 500 milliCPU per replica.
- Ensure sufficient CPU resources within the cluster to allocate a minimum of 100 milliCPU and a maximum of 200 milliCPU per replica.

## Parameters

Expand Down
2 changes: 1 addition & 1 deletion packs/hello-universe-1.1.3/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ You can deploy it using two preset configurations:

- If you are using the **Enable Hello Universe API** preset, you will need the `:3000` port available on your cluster too. Check out the [Usage](#usage) section for further details.

- Ensure sufficient CPU resources within the cluster to allocate a minimum of 500 milliCPU and a maximum of 500 milliCPU per replica.
- Ensure sufficient CPU resources within the cluster to allocate a minimum of 100 milliCPU and a maximum of 200 milliCPU per replica.

## Parameters

Expand Down
Loading

0 comments on commit 84d3826

Please sign in to comment.