-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Upstream
-
False
-
None
-
False
-
Impediment
-
- Bug Report
-
-
-
- What did you do?
-
-
The catalog-build target in Makefile still uses `opm index add` to generate a SQLite catalog index image. This needs to be updated to generating an FBC index image as we will be defaulting to using File-Based Catalogs once [PR](https://github.com/operator-framework/operator-sdk/pull/5809) is merged into master.
How reproducible:
Always
Steps to Reproduce:
1. generate an operator through operator-sdk
2. cat Makefile
-
-
-
- What did you expect to see?
-
-
Generate the FBC index image in the following way:
$ mkdir catalog
$ opm generate dockerfile catalog
$ mkdir catalog/xxxx
$ opm init xxxx -c alpha -o yaml > catalog/xxxx/index.yaml
$ opm render quay.io/test/xxxx:v1.0 -o yaml >> catalog/xxxx/index.yaml
-
-
-
- What did you see instead? Under which circumstances?
-
-
![Screen Shot 2022-06-06 at 11 27 34 AM](https://user-images.githubusercontent.com/3925702/172192770-e9e77744-dbab-4f27-9ccb-ecea01f939a9.png)
-
-
-
- Environment
-
-
`$ operator-sdk version`
operator-sdk version: "v1.20.0-16-g38b8b8d9", commit: "38b8b8d949578a44fb23319e56c242fd620523ca", kubernetes version: "v1.23", go version: "go1.17.4", GOOS: "linux", GOARCH: "amd64"
`$ go version` (if language is Go)
go version: "go1.17.4"
Upstream Github issue: https://github.com/operator-framework/operator-sdk/issues/5832
- is blocked by
-
OPECO-2605 operator authors have a path for automated catalog updates after bundle publishing
- Closed