Benjamin Huo
Benjamin Huo
> KubeEdge use hostnetwork while Kubesphere use nodeport, by default set to false to enable nodeport mode. This means we can change `hostNetWork: "{{ edgeruntime.kubeedge.cloudCore.hostNetWork | default("false", true) }}"` to...
> > KubeEdge use hostnetwork while Kubesphere use nodeport, by default set to false to enable nodeport mode. > > This means we can change `hostNetWork: "{{ edgeruntime.kubeedge.cloudCore.hostNetWork | default("false",...
@wanjunlei The new version fixed this?
@wanjunlei Do we have a wait period before actually sending the alert to feishu ?
Currently running KubeSphere on serverless K8s like fargate is not supported yet.
@junotx Is this a design limitation?
I think you can install any exporter on existing kubesphere
> The `generateID: true` should be added to the events and audit log receiver. `generateID: true` is related to the duplicated es log receivers? If generateID should be added to...
So you mean, we should change from the UI side to the same output value as the ks-installer?
`https://github.com/kubesphere/kubesphere/blob/master/pkg/client/listers/notification/v2beta1/` is KubeSphere's notification API version while `notification.kubesphere.io/v2beta2` is Notification Manager CRD version, they're not the same version actually.