---
# System prepended metadata

title: Untitled

---


### Phase 1: Initial e2e component workflow
- [x] Install operator-controller on cluster with the install script in repo
- [x] Build memcached operator from operator-sdk tutorials
- [x] Install operator with rukpak bundledeployment, verify CRDs on cluster
    create new FBC bundle, channel and package yaml for memcached operator image, build image from FBC
- [x] Deploy catalog with FBC image on cluster, verify packages+bundlemetadata
- [x] Create operator object for memcached operator, verify CRDs on cluster after install

<br>
<br>

### Phase 2: partial automation
- [x] Env setup script - Daniel's install script exists, takes optional arguments for desired rukpak, catalogd versions
- [ ] Script for image build+push (for bundle, FBC)
- [ ] Script for operator-sdk verify+build for given operator directory <b>(?)</b>
    - [ ] Alternatively, update kubectl to have manifests->bundle build
- [ ] Script for FBC generate (render only creates FBC from existing images)
- [ ] Script for operator object creation
- [ ] Post install verification script

<br>
<br>

### Phase 3: e2e automation (demo script)
- [ ]  Create e2e script from component scripts

<br>
<br>

### Phase 4: parameterization
- [ ] Custom operator object (provisioner/version/contraints)
- [ ] Custom operator source (prebuilt/from specific repository), Custom operaator-sdk version
- [ ] Custom FBC base
    - [ ] Custom FBC channel structure
    - [ ] Custom FBC properties additions
    - [ ] Adding into existing FBC
- [ ] image labels/specifications

<br>
<br>

### Phase 5: CI integration
- [ ] Integrate with github actions