Wanjun Lei
Wanjun Lei
https://github.com/kubesphere/kubesphere/blob/master/pkg/kapis/notification/v2beta1/register.go#L55 You can take a look at these api.
The v1beta1 API will sync the v1beta1 CRD to the member cluster and store it as v1beta2. There is no difference between the v1beta1 CRD and v2beta2 CRD in version...
First, apply all files in `https://github.com/kubesphere/notification-manager/tree/v2.0.0/helm/crds`. Second, update Notification Manage using helm ``` helm upgrade notification-manager --create-namespace -n kubesphere-monitoring-system https://github.com/kubesphere/notification-manager/releases/download/v2.0.0/notification-manager.tgz --set kubesphere=true ```
Hi @natalieparellano , the RFC had merged, what do I need to do next, start coding or update the platform API?
> Hi @wanjunlei, the final implementation requires several updates in different repositories. the following `tracking` [issue](https://github.com/buildpacks/rfcs/issues/246) was created to follow up that work. > > The issues there are marked...
你设置了一个127.0.0.1的goproxy，但是编译函数是在容器里进行的，是无法访问这个地址的，你要设置一个可以在容器内访问代理。
We do not recommend discussing different issues in one issue, you can open a new issue
The notification manager does not support NTLM auth, so change to another SMTP server.
> Yes, it's caused by the kubebuilder version. I think these changes should not be committed.
Private image repositories are not currently supported.