You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ted Chang (Jira)" <ji...@apache.org> on 2022/12/20 17:37:00 UTC

[jira] [Comment Edited] (FLINK-30456) OLM Bundle Description Version Problems

    [ https://issues.apache.org/jira/browse/FLINK-30456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17649882#comment-17649882 ] 

Ted Chang edited comment on FLINK-30456 at 12/20/22 5:36 PM:
-------------------------------------------------------------

Hi Jim,  could you also fix the LINKS showing n/a.
[https://operatorhub.io/operator/flink-kubernetes-operator]
!image-2022-12-20-08-21-02-597.png!

https://sdk.operatorframework.io/docs/olm-integration/generation/#csv-fields


was (Author: JIRAUSER287036):
Hi Jim,  could you also fix the LINKS showing n/a.
https://operatorhub.io/operator/flink-kubernetes-operator
!image-2022-12-20-08-21-02-597.png!

> OLM Bundle Description Version Problems
> ---------------------------------------
>
>                 Key: FLINK-30456
>                 URL: https://issues.apache.org/jira/browse/FLINK-30456
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.3.0
>            Reporter: James Busche
>            Assignee: James Busche
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: image-2022-12-20-08-21-02-597.png
>
>
> OLM is working great with OperatorHub, but noticed a few items that need fixing.
> 1.  The basic.yaml example version is release-1.1 instead of the latest release (release-1.3).  This needs fixing in two places:
> tools/olm/generate-olm-bundle.sh
> tools/olm/docker-entry.sh
> 2.  The label versions in the description are hardcoded to 1.2.0 instead of the latest release (1.3.0)
> 3. The Provider is blank space " " but soon needs to have some text in there to avoid CI errors with the latest operator-sdk versions.  The person who noticed it recommended "Community" for now, but maybe we can being making it "The Apache Software Foundation" now?  Not sure if we're ready for that yet or not...
>  
> I'm working on a PR to address these items.  Can you assign the issue to me?  Thanks!
> fyi [~tedhtchang] [~gyfora] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)