This repository has been archived by the owner on Apr 17, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add porch installation and Config sync installation from porch
- Loading branch information
Showing
25 changed files
with
1,961 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -21,7 +21,6 @@ spec: | |
displayName: packagename | ||
folderRef: | ||
name: environments | ||
namepace: environments-ns | ||
|
||
--- | ||
|
||
|
296 changes: 296 additions & 0 deletions
296
infra/porch/crds/config.porch.kpt.dev_remoterootsyncsets.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,296 @@ | ||
# Copyright 2022 Google LLC | ||
# | ||
# Licensed under the Apache License, Version 2.0 (the "License"); | ||
# you may not use this file except in compliance with the License. | ||
# You may obtain a copy of the License at | ||
# | ||
# http://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, software | ||
# distributed under the License is distributed on an "AS IS" BASIS, | ||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
|
||
--- | ||
apiVersion: apiextensions.k8s.io/v1 | ||
kind: CustomResourceDefinition | ||
metadata: | ||
annotations: | ||
controller-gen.kubebuilder.io/version: v0.8.0 | ||
creationTimestamp: null | ||
name: remoterootsyncsets.config.porch.kpt.dev | ||
spec: | ||
group: config.porch.kpt.dev | ||
names: | ||
kind: RemoteRootSyncSet | ||
listKind: RemoteRootSyncSetList | ||
plural: remoterootsyncsets | ||
singular: remoterootsyncset | ||
scope: Namespaced | ||
versions: | ||
- additionalPrinterColumns: | ||
- jsonPath: .status.aggregated.applied | ||
name: AppliedCount | ||
type: integer | ||
- jsonPath: .status.aggregated.ready | ||
name: ReadyCount | ||
type: integer | ||
- jsonPath: .status.aggregated.total | ||
name: Total | ||
type: integer | ||
- jsonPath: .status.aggregated.conditions[?(@.type=='Applied')].reason | ||
name: Applied | ||
type: string | ||
- jsonPath: .status.aggregated.conditions[?(@.type=='Ready')].reason | ||
name: Ready | ||
type: string | ||
name: v1alpha1 | ||
schema: | ||
openAPIV3Schema: | ||
description: "RemoteRootSyncSet represents applying a package to multiple | ||
target clusters. In future, this should use ConfigSync, but while we're | ||
iterating on OCI/porch support, and making a few similar iterations (e.g. | ||
what feedback do we need for rollout), we're just applying directly to the | ||
target cluster(s). \n We follow the \"managed remote objects\" pattern; | ||
we don't want to create a mirror object, so we start with the \"ReplicaSet\" | ||
of Pod/ReplicaSet/Deployment. \n spec.clusterRefs specifies the target clusters | ||
\n spec.template maps to the spec of our \"Pod\", in this case a ConfigSync | ||
RootSync/RepoSync. Because we're not actually using ConfigSync in this prototype, | ||
we are only defining a small subset of fields." | ||
properties: | ||
apiVersion: | ||
description: 'APIVersion defines the versioned schema of this representation | ||
of an object. Servers should convert recognized schemas to the latest | ||
internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources' | ||
type: string | ||
kind: | ||
description: 'Kind is a string value representing the REST resource this | ||
object represents. Servers may infer this from the endpoint the client | ||
submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds' | ||
type: string | ||
metadata: | ||
type: object | ||
spec: | ||
description: RemoteRootSyncSetSpec defines the desired state of RemoteRootSync | ||
properties: | ||
clusterRefs: | ||
items: | ||
properties: | ||
apiVersion: | ||
type: string | ||
kind: | ||
type: string | ||
name: | ||
type: string | ||
namespace: | ||
type: string | ||
type: object | ||
type: array | ||
template: | ||
properties: | ||
oci: | ||
description: Git *GitInfo `json:"git,omitempty"` | ||
properties: | ||
repository: | ||
type: string | ||
type: object | ||
sourceFormat: | ||
type: string | ||
type: object | ||
type: object | ||
status: | ||
description: RootSyncSetStatus defines the observed state of RootSyncSet | ||
properties: | ||
aggregated: | ||
properties: | ||
applied: | ||
format: int32 | ||
type: integer | ||
conditions: | ||
description: Conditions describes the reconciliation state of | ||
the object. | ||
items: | ||
description: "Condition contains details for one aspect of the | ||
current state of this API Resource. --- This struct is intended | ||
for direct use as an array at the field path .status.conditions. | ||
\ For example, type FooStatus struct{ // Represents the observations | ||
of a foo's current state. // Known .status.conditions.type | ||
are: \"Available\", \"Progressing\", and \"Degraded\" // +patchMergeKey=type | ||
// +patchStrategy=merge // +listType=map // +listMapKey=type | ||
Conditions []metav1.Condition `json:\"conditions,omitempty\" | ||
patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"` | ||
\n // other fields }" | ||
properties: | ||
lastTransitionTime: | ||
description: lastTransitionTime is the last time the condition | ||
transitioned from one status to another. This should be | ||
when the underlying condition changed. If that is not | ||
known, then using the time when the API field changed | ||
is acceptable. | ||
format: date-time | ||
type: string | ||
message: | ||
description: message is a human readable message indicating | ||
details about the transition. This may be an empty string. | ||
maxLength: 32768 | ||
type: string | ||
observedGeneration: | ||
description: observedGeneration represents the .metadata.generation | ||
that the condition was set based upon. For instance, if | ||
.metadata.generation is currently 12, but the .status.conditions[x].observedGeneration | ||
is 9, the condition is out of date with respect to the | ||
current state of the instance. | ||
format: int64 | ||
minimum: 0 | ||
type: integer | ||
reason: | ||
description: reason contains a programmatic identifier indicating | ||
the reason for the condition's last transition. Producers | ||
of specific condition types may define expected values | ||
and meanings for this field, and whether the values are | ||
considered a guaranteed API. The value should be a CamelCase | ||
string. This field may not be empty. | ||
maxLength: 1024 | ||
minLength: 1 | ||
pattern: ^[A-Za-z]([A-Za-z0-9_,:]*[A-Za-z0-9_])?$ | ||
type: string | ||
status: | ||
description: status of the condition, one of True, False, | ||
Unknown. | ||
enum: | ||
- "True" | ||
- "False" | ||
- Unknown | ||
type: string | ||
type: | ||
description: type of condition in CamelCase or in foo.example.com/CamelCase. | ||
--- Many .condition.type values are consistent across | ||
resources like Available, but because arbitrary conditions | ||
can be useful (see .node.status.conditions), the ability | ||
to deconflict is important. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt) | ||
maxLength: 316 | ||
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ | ||
type: string | ||
required: | ||
- lastTransitionTime | ||
- message | ||
- reason | ||
- status | ||
- type | ||
type: object | ||
type: array | ||
ready: | ||
format: int32 | ||
type: integer | ||
total: | ||
format: int32 | ||
type: integer | ||
required: | ||
- applied | ||
- ready | ||
- total | ||
type: object | ||
targets: | ||
items: | ||
properties: | ||
conditions: | ||
description: Conditions describes the reconciliation state of | ||
the object. | ||
items: | ||
description: "Condition contains details for one aspect of | ||
the current state of this API Resource. --- This struct | ||
is intended for direct use as an array at the field path | ||
.status.conditions. For example, type FooStatus struct{ | ||
// Represents the observations of a foo's current state. | ||
// Known .status.conditions.type are: \"Available\", \"Progressing\", | ||
and \"Degraded\" // +patchMergeKey=type // +patchStrategy=merge | ||
// +listType=map // +listMapKey=type Conditions []metav1.Condition | ||
`json:\"conditions,omitempty\" patchStrategy:\"merge\" patchMergeKey:\"type\" | ||
protobuf:\"bytes,1,rep,name=conditions\"` \n // other fields | ||
}" | ||
properties: | ||
lastTransitionTime: | ||
description: lastTransitionTime is the last time the condition | ||
transitioned from one status to another. This should | ||
be when the underlying condition changed. If that is | ||
not known, then using the time when the API field changed | ||
is acceptable. | ||
format: date-time | ||
type: string | ||
message: | ||
description: message is a human readable message indicating | ||
details about the transition. This may be an empty string. | ||
maxLength: 32768 | ||
type: string | ||
observedGeneration: | ||
description: observedGeneration represents the .metadata.generation | ||
that the condition was set based upon. For instance, | ||
if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration | ||
is 9, the condition is out of date with respect to the | ||
current state of the instance. | ||
format: int64 | ||
minimum: 0 | ||
type: integer | ||
reason: | ||
description: reason contains a programmatic identifier | ||
indicating the reason for the condition's last transition. | ||
Producers of specific condition types may define expected | ||
values and meanings for this field, and whether the | ||
values are considered a guaranteed API. The value should | ||
be a CamelCase string. This field may not be empty. | ||
maxLength: 1024 | ||
minLength: 1 | ||
pattern: ^[A-Za-z]([A-Za-z0-9_,:]*[A-Za-z0-9_])?$ | ||
type: string | ||
status: | ||
description: status of the condition, one of True, False, | ||
Unknown. | ||
enum: | ||
- "True" | ||
- "False" | ||
- Unknown | ||
type: string | ||
type: | ||
description: type of condition in CamelCase or in foo.example.com/CamelCase. | ||
--- Many .condition.type values are consistent across | ||
resources like Available, but because arbitrary conditions | ||
can be useful (see .node.status.conditions), the ability | ||
to deconflict is important. The regex it matches is | ||
(dns1123SubdomainFmt/)?(qualifiedNameFmt) | ||
maxLength: 316 | ||
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$ | ||
type: string | ||
required: | ||
- lastTransitionTime | ||
- message | ||
- reason | ||
- status | ||
- type | ||
type: object | ||
type: array | ||
ref: | ||
properties: | ||
apiVersion: | ||
type: string | ||
kind: | ||
type: string | ||
name: | ||
type: string | ||
namespace: | ||
type: string | ||
type: object | ||
type: object | ||
type: array | ||
type: object | ||
type: object | ||
served: true | ||
storage: true | ||
subresources: | ||
status: {} | ||
status: | ||
acceptedNames: | ||
kind: "" | ||
plural: "" | ||
conditions: [] | ||
storedVersions: [] |
Oops, something went wrong.