Skip to content

Commit

Permalink
Add gen
Browse files Browse the repository at this point in the history 
Signed-off-by: Gidi233 <[email protected]>
  • Loading branch information
@Gidi233
Gidi233 committed Sep 2, 2024
1 parent 9c9a619 commit f42c88f
Show file tree
Hide file tree
Showing 5 changed files with 214 additions and 5 deletions.
53 changes: 50 additions & 3 deletions docs/content/en/references/apps_v1alpha1_types.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1707,13 +1707,12 @@ <h3 id="apps.kurator.dev/v1alpha1.RolloutConfig">RolloutConfig
<td>
<code>trafficRoutingProvider</code><br>
<em>
string
Kurator fleet/v1alpha1.Provider
</em>
</td>
<td>
<em>(Optional)</em>
<p>TrafficRoutingProvider defines traffic routing provider.
Kurator only supports istio for now.
Kurator supports istio,kuma,nginx for now.
Other provider will be added later.</p>
</td>
</tr>
Expand Down Expand Up @@ -2213,6 +2212,54 @@ <h3 id="apps.kurator.dev/v1alpha1.TrafficRoutingConfig">TrafficRoutingConfig
</tr>
<tr>
<td>
<code>host</code><br>
<em>
string
</em>
</td>
<td>
<em>(Optional)</em>
<p>for NGINX
The default created ingress is as follows, (Fill in <code>host</code> with your own domain)</p>
<pre><code class="language-yaml">apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: nginx
namespace: application.syncPolicies.rollout.workload.namespace
labels:
app: application.syncPolicies.rollout.ServiceName
annotations:
kubernetes.io/ingress.class: &quot;nginx&quot;
spec:
rules:
- host: &quot;&quot;
http:
paths:
- pathType: Prefix
path: &quot;/&quot;
backend:
service:
name: application.syncPolicies.rollout.ServiceName
port:
number: application.syncPolicies.rollout.port
</code></pre>
</td>
</tr>
<tr>
<td>
<code>protocol</code><br>
<em>
string
</em>
</td>
<td>
<em>(Optional)</em>
<p>for kuma
Defaults to http</p>
</td>
</tr>
<tr>
<td>
<code>canaryStrategy</code><br>
<em>
<a href="#apps.kurator.dev/v1alpha1.CanaryConfig">
Expand Down
68 changes: 67 additions & 1 deletion docs/content/en/references/fleet_v1alpha1_types.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -338,6 +338,7 @@ <h3 id="fleet.kurator.dev/v1alpha1.ChartConfig">ChartConfig
<p>
(<em>Appears on:</em>
<a href="#fleet.kurator.dev/v1alpha1.BackupConfig">BackupConfig</a>,
<a href="#fleet.kurator.dev/v1alpha1.Config">Config</a>,
<a href="#fleet.kurator.dev/v1alpha1.DistributedStorageConfig">DistributedStorageConfig</a>,
<a href="#fleet.kurator.dev/v1alpha1.FlaggerConfig">FlaggerConfig</a>,
<a href="#fleet.kurator.dev/v1alpha1.GrafanaConfig">GrafanaConfig</a>,
Expand Down Expand Up @@ -399,6 +400,56 @@ <h3 id="fleet.kurator.dev/v1alpha1.ChartConfig">ChartConfig
</table>
</div>
</div>
<h3 id="fleet.kurator.dev/v1alpha1.Config">Config
</h3>
<p>
(<em>Appears on:</em>
<a href="#fleet.kurator.dev/v1alpha1.FlaggerConfig">FlaggerConfig</a>)
</p>
<div class="md-typeset__scrollwrap">
<div class="md-typeset__table td-content">
<table>
<thead>
<tr>
<th>Field</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>
<code>chart</code><br>
<em>
<a href="#fleet.kurator.dev/v1alpha1.ChartConfig">
ChartConfig
</a>
</em>
</td>
<td>
<em>(Optional)</em>
<p>Chart defines the helm chart config of the TrafficRoutingProvider.
default value is in ./pkg/fleet-manager/manifests/plugins/</p>
</td>
</tr>
<tr>
<td>
<code>extraArgs</code><br>
<em>
<a href="https://pkg.go.dev/k8s.io/apiextensions-apiserver/pkg/apis/apiextensions/v1?tab=doc#JSON">
Kubernetes /apiextensions/v1.JSON
</a>
</em>
</td>
<td>
<em>(Optional)</em>
<p>ExtraArgs is the set of extra arguments for TrafficRoutingProvider&rsquo;s chart.
You can pass in values according to your needs.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<h3 id="fleet.kurator.dev/v1alpha1.Device">Device
</h3>
<p>
Expand Down Expand Up @@ -665,10 +716,11 @@ <h3 id="fleet.kurator.dev/v1alpha1.FlaggerConfig">FlaggerConfig
</em>
</td>
<td>
<em>(Optional)</em>
<p>TrafficRoutingProvider defines traffic routing provider.
And Kurator will install flagger in trafficRoutingProvider&rsquo;s namespace
For example, If you use <code>istio</code> as a provider, flager will be installed in istio&rsquo;s namespace <code>istio-system</code>.
And if you use <code>istio</code> as a provider, you need to install it manually.
Otherwise, you can configure it in ProviderConfig (or use the default configuration) and Kurator will automatically deploy it.
Other provider will be added later.</p>
</td>
</tr>
Expand All @@ -685,6 +737,20 @@ <h3 id="fleet.kurator.dev/v1alpha1.FlaggerConfig">FlaggerConfig
you can also specify a private testloader in the Application.Spec.SyncPolicies.Rollout.TestLoader</p>
</td>
</tr>
<tr>
<td>
<code>Config</code><br>
<em>
<a href="#fleet.kurator.dev/v1alpha1.Config">
Config
</a>
</em>
</td>
<td>
<em>(Optional)</em>
<p>ProviderConfig defines the configuration for the TrafficRoutingProvider.</p>
</td>
</tr>
</tbody>
</table>
</div>
Expand Down
36 changes: 35 additions & 1 deletion manifests/charts/fleet-manager/crds/apps.kurator.dev_applications.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1618,6 +1618,34 @@ spec:
type: object
type: object
type: object
host:
description: |-
for NGINX
The default created ingress is as follows, (Fill in `host` with your own domain)
```yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: nginx
namespace: application.syncPolicies.rollout.workload.namespace
labels:
app: application.syncPolicies.rollout.ServiceName
annotations:
kubernetes.io/ingress.class: "nginx"
spec:
rules:
- host: ""
http:
paths:
- pathType: Prefix
path: "/"
backend:
service:
name: application.syncPolicies.rollout.ServiceName
port:
number: application.syncPolicies.rollout.port
```
type: string
hosts:
description: Defaults to the RolloutConfig.ServiceName
items:
Expand Down Expand Up @@ -1923,6 +1951,11 @@ spec:
type: object
type: object
type: array
protocol:
description: |-
for kuma
Defaults to http
type: string
retries:
description: |-
Retries describes the retry policy to use when a HTTP request fails.
Expand Down Expand Up @@ -1978,7 +2011,7 @@ spec:
trafficRoutingProvider:
description: |-
TrafficRoutingProvider defines traffic routing provider.
Kurator only supports istio for now.
Kurator supports istio,kuma,nginx for now.
Other provider will be added later.
type: string
workload:
Expand All @@ -2005,6 +2038,7 @@ spec:
- port
- rolloutPolicy
- serviceName
- trafficRoutingProvider
- workload
type: object
type: object
Expand Down
35 changes: 35 additions & 0 deletions manifests/charts/fleet-manager/crds/fleet.kurator.dev_fleets.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2465,6 +2465,37 @@ spec:
description: Flagger defines the configuration for the kurator
rollout engine.
properties:
Config:
description: ProviderConfig defines the configuration for
the TrafficRoutingProvider.
properties:
chart:
description: |-
Chart defines the helm chart config of the TrafficRoutingProvider.
default value is in ./pkg/fleet-manager/manifests/plugins/
properties:
name:
description: |-
Name defines the name of the chart.
Default value depends on the kind of the component.
type: string
repository:
description: |-
Repository defines the repository of chart.
Default value depends on the kind of the component.
type: string
version:
description: |-
Version defines the version of the chart.
Default value depends on the kind of the component.
type: string
type: object
extraArgs:
description: |-
ExtraArgs is the set of extra arguments for TrafficRoutingProvider's chart.
You can pass in values according to your needs.
x-kubernetes-preserve-unknown-fields: true
type: object
chart:
description: |-
Chart defines the helm chart config of the flagger.
Expand Down Expand Up @@ -2517,8 +2548,12 @@ spec:
TrafficRoutingProvider defines traffic routing provider.
And Kurator will install flagger in trafficRoutingProvider's namespace
For example, If you use `istio` as a provider, flager will be installed in istio's namespace `istio-system`.
And if you use `istio` as a provider, you need to install it manually.
Otherwise, you can configure it in ProviderConfig (or use the default configuration) and Kurator will automatically deploy it.
Other provider will be added later.
type: string
required:
- trafficRoutingProvider
type: object
grafana:
description: Grafana defines the configuration for the grafana
Expand Down
27 changes: 27 additions & 0 deletions pkg/apis/fleet/v1alpha1/zz_generated.deepcopy.go
View file

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit f42c88f

Please sign in to comment.