Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Mark Nelson
    @markxnelson
    @resouer Hi Ryan, I am looking at the oam-kubernetes-runtime adoption, as we have discussed before. As part of that, I am looking at the third party dependencies, versions, checking if there are any known security vulnerabilities, etc. I am seeing that there are some dependencies that are using very old versions, and this is a concern for us. Can you tell me if there are any plans to bring these up to date? Or any reason why they cannot be brought up to date? Thanks
    Lei Zhang (Harry)
    @resouer
    Hi @markxnelson , there's no any blocker to bump the dependency versions, though we normally do this only per requirement or fixing bugs. Could you please let us know if there's any specific out-of-date dependency you have concern with? Happy to ship upgrade in upcoming release.
    Mark Nelson
    @markxnelson
    Thanks Harry, I will get back to you soon.
    Lei Zhang (Harry)
    @resouer
    Hi folks, in today's meeting, we will talk about: oam-dev/spec#412
    as well as some general ideas regarding to KubeVela: https://github.com/oam-dev/kubevela/blob/master/DESIGN.md
    Lei Zhang (Harry)
    @resouer
    FYI, we've fixed the previous zoom meeting link : https://zoom.us/j/271516061
    Lei Zhang (Harry)
    @resouer
    Hi folks, in today's community meeting we will update some recent progress on the spec and implementations! Join us: https://zoom.us/j/271516061
    Darrell
    @dazinator
    Hi all. I was wondering if SF Mesh will support OAM deployments?
    SF Mesh has a lot of fancy (but old) documentation indicating it's a hosting "Nirvanna" but ideally I would want to describe my application with a model that could be potentially deployed elsewhere - enter OAM.
    Lei Zhang (Harry)
    @resouer
    Hi @dazinator, for now the community side doesn't have plan to implement OAM on SF Mesh AFAIK. But in high level, OAM maintainers including MSFT folks are actively working on making OAM to be easier implemented on various platforms. This may help the community make SF Mesh support happen in the future.
    Darrell
    @dazinator
    @resouer ok, thank you!
    NOMAD
    @motecshine
    @resouer how can i use route traits only create kubernetes service, because our some application only serving internal
    Lei Zhang (Harry)
    @resouer
    @motecshine yes, route trait will automatically generate k8s service for you workload.
    Also, in the future, KubeVela will automatically generate k8s service for any Web Service type
    Kevin Minder
    @kminder
    Is there a meeting today?
    Artur Souza
    @artursouza
    I am also connecting to the meeting, it says host has not started the meeting.
    Lei Zhang (Harry)
    @resouer
    Hi folks, please join with the link in google doc
    @kminder yes, please check the meeting link above
    Lei Zhang (Harry)
    @resouer
    Hey! The bi-weekly #oam community (NA time zone) meeting starts at 10:30AM PST! We will share #GitOps + OAM, updates from KubeVela project, several new ideas on OAM spec and more! Come and join: https://docs.google.com/document/d/1nqdFEyULekyksFHtFvgvFAYE-0AMHKoS3RMnaKsarjs/edit#
    Alvaro Agea
    @aagea
    Hi folks, is there a community call today?
    Hongchao Deng
    @hongchaodeng
    @aagea No community meeting today due to holidays
    Incubator4th
    @Incubator4th
    hello everyone,I got some confusion about kubevela.Should vela be used in ci cd pipeline?
    Lei Zhang (Harry)
    @resouer
    @Incubator4th yes, you can use vela with any CI/CD pipeline. you can also use vela with GitOps if you prefer: https://www.cncf.io/blog/2020/12/22/argocd-kubevela-gitops-with-developer-centric-experience/
    Incubator4th
    @Incubator4th
    Current we use kustomize with yaml resource and helm chart for package version manager.But it seems vela didn’t consider about that,which I means it’s not a perfect solution
    Lei Zhang (Harry)
    @resouer
    @Incubator4th Vela has a CRD named Application which is equivalent to appfile in server side, so you can use it with kustomize, helm or any other k8s yaml manipulator you like.
    Incubator4th
    @Incubator4th
    @resouer thx,I will check that and may not reply soon.Sorry about I don’t know about that.whatever,thanks
    Lei Zhang (Harry)
    @resouer
    @Incubator4th No worries! Application CRD is indeed pretty new so we have no doc for it for now, please feel free to check its type structure here: https://github.com/oam-dev/kubevela/blob/master/apis/core.oam.dev/v1alpha2/application_types.go
    Incubator4th
    @Incubator4th
    @resouer I briefly browsed it.I wonder why vela file is not first translated into this Application CR and then got chain CRD call.because I tried demo app and did not found application resource in Cluster
    Lei Zhang (Harry)
    @resouer
    @Incubator4th The final piece is WIP but close to merge here: oam-dev/kubevela#846, for now, appfile is rendered into Component + ApplicationConfiguration.
    Lee Calcote
    @leecalcote
    Hi All, is the next OAM community meeting tomorrow (Jan 12th)?
    Lei Zhang (Harry)
    @resouer
    @leecalcote That's correct!
    Lee Calcote
    @leecalcote
    Very good. :)
    Lei Zhang (Harry)
    @resouer
    @leecalcote Welcome the community btw, Lee! If there's any specific topic/issue/question you want to bring up, feel free to add them on the meeting note: https://docs.google.com/document/d/1nqdFEyULekyksFHtFvgvFAYE-0AMHKoS3RMnaKsarjs/edit#
    Kevin Minder
    @kminder

    We are experiencing timing issues with the application of changes resulting from trait and scope processing to application resources. In particular we have an example of workload type of which known customer applications can take several minutes to start or restart. The implementation model suggested by the oam-kubernetes-runtime is to update the application’s workload resource or its eventual children resources after they are created. This is causing the application to be restarted since the operator typically begins processing the resources when they are first created and may then need to restart them when a change is later detected. In addition we cannot guarantee that a user’s application will not lose data if it is restarted unexpectedly.

    As a result, having an OAM standard way to apply changes for traits and scopes to workloads before the workload resources are actually created will be important for us.
    How can this be done?

    Kevin Minder
    @kminder
    Created oam-dev/spec#425 to continue the conversation on the issue above.
    Mark Nelson
    @markxnelson
    Hi @resouer @ryanzhang-oss, could you please confirm for me who is the copyright holder for the spec itself? I can't find a copyright notice in the repo. Is it CNCF?
    Lei Zhang (Harry)
    @resouer
    @markxnelson Hi, it's the Open Web Foundation (OWF), this is mentioned in the announcement blog of OAM spec: https://cloudblogs.microsoft.com/opensource/2019/10/16/announcing-open-application-model/
    Mark Nelson
    @markxnelson
    is there any way you could add a copyright notice in the spec's readme to make that clear?
    Maybe we should bring a separate section in README?
    Mark Nelson
    @markxnelson
    sorry to ask, but our lawyers are going to want to see it stated very explicitly in the repo before they allow us to contribute
    that statement in the contributing doc really says contributions will be subject to those terms, etc., but it does not say who the copyright holder is
    Lei Zhang (Harry)
    @resouer
    I see, we could definitionly fix it by providing a statement in README of the spec
    Mark Nelson
    @markxnelson
    that would help me a lot, thanks
    1 reply
    Alvaro Agea
    @aagea
    Hi all, we are advancing in the development of our MVP and during testing have found a behavior that we believe may be a bug on the runtime.
    8 replies
    BHANUPRAKASHMS
    @BHANUPRAKASHMS
    hi All I am new to OAM
    Lei Zhang (Harry)
    @resouer
    @BHANUPRAKASHMS Welcome!
    Holger Protzek
    @hprotzek
    Hi there, we would like to give kubevela a try and install it into our existing gke dev cluster. Due the dependencies of prometheus operator and cert-manager this is not possible right now. Are you open for a PR to make these dependencies in the helm chart optional?
    Lei Zhang (Harry)
    @resouer
    @hprotzek Yes of course! Note that the 3rd-party dependencies are configurable via a ConfigMap, please check this doc: https://kubevela.io/#/en/install?id=_3-initialize-kubevela, "Customize Your Installation" section, hope that could solve your problem.