You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR reorganizes sdk.operatorframework.io to match the navigation panel for olm.operatorframework.io, so that both the sites appear to be part of one operator-framework family.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -220,7 +220,7 @@
220
220
- The type name `TestCtx` in `pkg/test` has been deprecated and renamed to `Context`. It now exists only as a type alias to maintain backwards compatibility. Users of the e2e framework should migrate to use the new name, `Context`. The `TestCtx` alias will be removed in a future version. ([2549](https://github.com/operator-framework/operator-sdk/pull/2549))
221
221
222
222
- The additional of the dependency `inotify-tools` on Ansible based-operator images. ([#2586](https://github.com/operator-framework/operator-sdk/pull/2586))
223
-
-**Breaking Change:** The scorecard feature now only supports YAML config files. So, any config file with other extension is deprecated and should be changed for the YAML format. For further information see [`scorecard config file`](./website/content/en/docs/scorecard/_index.md#config-file) ([#2591](https://github.com/operator-framework/operator-sdk/pull/2591))
223
+
-**Breaking Change:** The scorecard feature now only supports YAML config files. So, any config file with other extension is deprecated and should be changed for the YAML format. For further information see [`scorecard config file`](./website/content/en/docs/advanced-topics/scorecard/_index.md#config-file) ([#2591](https://github.com/operator-framework/operator-sdk/pull/2591))
224
224
225
225
### Removed
226
226
@@ -465,7 +465,7 @@
465
465
466
466
### Changed
467
467
468
-
- **Breaking Change:** New configuration format for the `operator-sdk scorecard` using config files. See [`doc/test-framework/scorecard`](./website/content/en/docs/scorecard/_index.md) for more info ([#1641](https://github.com/operator-framework/operator-sdk/pull/1641))
468
+
- **Breaking Change:** New configuration format for the `operator-sdk scorecard` using config files. See [`doc/test-framework/scorecard`](./website/content/en/docs/advanced-topics/scorecard/_index.md) for more info ([#1641](https://github.com/operator-framework/operator-sdk/pull/1641))
469
469
- **Breaking change:** CSV config field `role-path` is now `role-paths` and takes a list of strings. Users can now specify multiple `Role` and `ClusterRole` manifests using `role-paths`. ([#1704](https://github.com/operator-framework/operator-sdk/pull/1704))
470
470
- Make`ready`package idempotent. Now, a user can call `Set()` or `Unset()` to set the operator's readiness without knowing the current state. ([#1761](https://github.com/operator-framework/operator-sdk/pull/1761))
471
471
@@ -534,7 +534,7 @@
534
534
- Unify CLI debug logging under a global `--verbose` flag ([#1361](https://github.com/operator-framework/operator-sdk/pull/1361))
535
535
- [Go module](https://github.com/golang/go/wiki/Modules) support by default for new Go operators and during Ansible and Helm operator migration. The dependency manager used for a new operator can be explicitly specified for new operators through the `--dep-manager` flag, available in [`operator-sdk new`](https://github.com/operator-framework/operator-sdk/blob/v0.8.0/doc/sdk-cli-reference.md#new) and [`operator-sdk migrate`](https://github.com/operator-framework/operator-sdk/blob/v0.8.0/doc/sdk-cli-reference.md#migrate). `dep` is still available through `--dep-manager=dep`. ([#1001](https://github.com/operator-framework/operator-sdk/pull/1001))
536
536
- New optional flag `--custom-api-import` for [`operator-sdk add controller`](https://github.com/operator-framework/operator-sdk/blob/v0.8.0/doc/sdk-cli-reference.md#controller) to specify that the new controller reconciles a built-in or external Kubernetes API, and what import path and identifier it should have. ([#1344](https://github.com/operator-framework/operator-sdk/pull/1344))
537
-
- Operator Scorecard plugin support. Documentation for scorecard plugins can be found in the main scorecard [doc](./website/content/en/docs/scorecard/_index.md). ([#1379](https://github.com/operator-framework/operator-sdk/pull/1379))
537
+
- Operator Scorecard plugin support. Documentation for scorecard plugins can be found in the main scorecard [doc](./website/content/en/docs/advanced-topics/scorecard/_index.md). ([#1379](https://github.com/operator-framework/operator-sdk/pull/1379))
538
538
539
539
### Changed
540
540
@@ -650,7 +650,7 @@
650
650
- Ansible operator proxy added the cache handler which allows the get requests to use the operators cache. [#760](https://github.com/operator-framework/operator-sdk/pull/760)
651
651
- Ansible operator proxy added ability to dynamically watch dependent resource that were created by ansible operator. [#857](https://github.com/operator-framework/operator-sdk/pull/857)
652
652
- Ansible-based operators have leader election turned on by default. When upgrading, add environment variable `POD_NAME` to your operator's Deployment using the Kubernetes downward API. To see an example, run `operator-sdk new --type=ansible ...` and see file `deploy/operator.yaml`.
653
-
- A new command [`operator-sdk scorecard`](https://github.com/operator-framework/operator-sdk/blob/v0.4.0/doc/sdk-cli-reference.md#scorecard) which runs a series of generic tests on operators to ensure that an operator follows best practices. For more information, see the [scorecard documentation](./website/content/en/docs/scorecard/_index.md)
653
+
- A new command [`operator-sdk scorecard`](https://github.com/operator-framework/operator-sdk/blob/v0.4.0/doc/sdk-cli-reference.md#scorecard) which runs a series of generic tests on operators to ensure that an operator follows best practices. For more information, see the [scorecard documentation](./website/content/en/docs/advanced-topics/scorecard/_index.md)
Copy file name to clipboardExpand all lines: website/content/en/build/_index.html
+9-9Lines changed: 9 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -24,14 +24,14 @@ <h2 class="of-heading of-heading--md">How can I write an Operator with Operator
24
24
<divclass="of-section--largetext__item">
25
25
<h2class="of-heading of-heading--xl">Installing the SDK CLI</h2>
26
26
<divclass="of-section--largetext__content">
27
-
<p>Follow the steps in the <ahref="/docs/install-operator-sdk/">installation guide</a> to learn how to install the Operator SDK CLI tool. If you are using a release version of the SDK, make sure to follow the documentation for that version. You make use any of the following installation processes:</p>
27
+
<p>Follow the steps in the <ahref="/docs/installation/install-operator-sdk/">installation guide</a> to learn how to install the Operator SDK CLI tool. If you are using a release version of the SDK, make sure to follow the documentation for that version. You make use any of the following installation processes:</p>
28
28
<olclass="of-list-ordered">
29
-
<li>Install the <ahref="/docs/install-operator-sdk/#install-from-homebrew-macos">Homebrew</a> (macOS)</li>
30
-
<li>Install from <ahref="/docs/install-operator-sdk/#install-from-github-release">GitHub</a> release</li>
31
-
<li>Compile and install from <ahref="/docs/install-operator-sdk/#compile-and-install-from-master">master</a></li>
29
+
<li>Install the <ahref="/docs/installation/install-operator-sdk/#install-from-homebrew-macos">Homebrew</a> (macOS)</li>
30
+
<li>Install from <ahref="/docs/installation/install-operator-sdk/#install-from-github-release">GitHub</a> release</li>
31
+
<li>Compile and install from <ahref="/docs/installation/install-operator-sdk/#compile-and-install-from-master">master</a></li>
32
32
</ol>
33
33
</div>
34
-
<ahref="/docs/install-operator-sdk" class="of-button of-button--tertiary">Learn More
34
+
<ahref="/docs/installation/install-operator-sdk" class="of-button of-button--tertiary">Learn More
@@ -44,19 +44,19 @@ <h2 class="of-heading of-heading--xl">Installing the SDK CLI</h2>
44
44
<h2class="of-heading of-heading--xl">READ THE USER GUIDES</h2>
45
45
<pclass="of-section--largetext__content">Operators can be created with the SDK using Ansible, Helm, or Go. Follow the one of the quickstart guides to dive in.</p>
Copy file name to clipboardExpand all lines: website/content/en/docs/_index.md
-89Lines changed: 0 additions & 89 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,92 +6,3 @@ menu:
6
6
weight: 2
7
7
---
8
8
9
-
## Overview
10
-
11
-
This project is a component of the [Operator Framework][of-home], an open source toolkit to manage Kubernetes native applications, called Operators, in an effective, automated, and scalable way. Read more in the [introduction blog post][of-blog].
12
-
13
-
[Operators][operator_link] make it easy to manage complex stateful applications on top of Kubernetes. However writing an operator today can be difficult because of challenges such as using low level APIs, writing boilerplate, and a lack of modularity which leads to duplication.
14
-
15
-
The Operator SDK is a framework that uses the [controller-runtime][controller_runtime] library to make writing operators easier by providing:
16
-
17
-
- High level APIs and abstractions to write the operational logic more intuitively
18
-
- Tools for scaffolding and code generation to bootstrap a new project fast
19
-
- Extensions to cover common operator use cases
20
-
21
-
## Workflow
22
-
23
-
The SDK provides workflows to develop operators in Go, Ansible, or Helm.
24
-
25
-
The following workflow is for a new [Golang operator][golang-guide]:
26
-
27
-
1. Create a new operator project using the SDK Command Line Interface(CLI)
28
-
2. Define new resource APIs by adding Custom Resource Definitions(CRD)
29
-
3. Define Controllers to watch and reconcile resources
30
-
4. Write the reconciling logic for your Controller using the SDK and controller-runtime APIs
31
-
5. Use the SDK CLI to build and generate the operator deployment manifests
32
-
33
-
The following workflow is for a new [Ansible operator][ansible-guide]:
34
-
35
-
1. Create a new operator project using the SDK Command Line Interface(CLI)
36
-
2. Write the reconciling logic for your object using ansible playbooks and roles
37
-
3. Use the SDK CLI to build and generate the operator deployment manifests
38
-
4. Optionally add additional CRD's using the SDK CLI and repeat steps 2 and 3
39
-
40
-
The following workflow is for a new [Helm operator][helm-guide]:
41
-
42
-
1. Create a new operator project using the SDK Command Line Interface(CLI)
43
-
2. Create a new (or add your existing) Helm chart for use by the operator's reconciling logic
44
-
3. Use the SDK CLI to build and generate the operator deployment manifests
45
-
4. Optionally add additional CRD's using the SDK CLI and repeat steps 2 and 3
46
-
47
-
## Command Line Interface
48
-
49
-
To learn more about the SDK CLI, see the [SDK CLI Reference][sdk_cli_ref], or run `operator-sdk [command] -h`.
50
-
51
-
### Operator capability level
52
-
53
-
Note that each operator type has a different set of capabilities. When choosing what type to use for your project, it is important to understand the features and limitations of each of the project types and the use cases for your operator.
0 commit comments