TCS Confidential Hi Shu Kit
Here is the summary of changes. Informers watch the ATSCaching CRD for create, update, and delete events and notify the controller. The controller then triggers the respective Add, Update, or Delete handler functions. For Add and Update events, the url_regex and ttl values are fetched from the CRD and updates are done cache.config file. For Delete events, handler removes the corresponding entries from the cache.config. This mechanism ensures that the cache configuration always stays in sync with the ATSCaching CRD. When an update is done in cache.config file there is also traffic_ctl config reload command executed (similar to updates for Config) regards, Saurabh ________________________________ From: Shu Kit Chan <chanshu...@gmail.com> Sent: Friday, August 15, 2025 05:06 To: dev@trafficserver.apache.org <dev@trafficserver.apache.org> Subject: Re: New Feature - Kubernetes Operator Creation External Email : Be cautious while opening any links or attachments. That looks ok as a first step. But I think it may be better for you to list out the functionality you want the operator to support. So then we can see how each of them can be supported through different CRD and have a debate about it. It is perfectly fine to start a conversation on the issue first. If it goes too long, we can discuss how to manage the conversation later. Thanks. Kit On Thu, Aug 14, 2025 at 6:33 AM Saurabh Saraswat <saurabh.saras...@tcs.com.invalid> wrote: > > TCS Confidential > > Hi Shu kit Chan, > > As first stab, we are creating a CRD for basic caching functionality. > Should I create a issue and then create pull request corresponding to it ? > > Here is what CRD looks like: > kind: ATSCachingPolicy > metadata: > name: my-app-caching > namespace: caching-ats-new > spec: > rules: > - name: home-page > primarySpecifier: > type: url_regex > pattern: "^/test" > action: cache > ttl: "10s" > - name: home-endpoint > primarySpecifier: > type: url_regex > pattern: ".*/app1" > action: cache > ttl: "15s" > - name: static-assets > primarySpecifier: > type: url_regex > pattern: "^/app2" > action: cache > ttl: "20s" > > > > regards, > saurabh > ________________________________ > From: Shu Kit Chan <chanshu...@gmail.com> > Sent: Friday, July 4, 2025 05:56 > To: dev@trafficserver.apache.org <dev@trafficserver.apache.org> > Subject: Re: New Feature - Kubernetes Operator Creation > > External Email : Be cautious while opening any links or attachments. > > This is an open source project hosted on github. > And it is Apache License 2.0 > So anyone is welcome to participate and submit pull requests to the > repository. > > As far as I know, i am the only one working on this repository at the > moment. I have been looking to add/maintain helm chart as well as > making a kubernetes operator for it. Also I would like to add support > for the gateway API as well. But obviously as you can see, I have not > been able to find time for all these activities. > > My recommendation is to use this repo as base and add support for > operator on top of it > > Thanks. > > Kit > > On Wed, Jul 2, 2025 at 10:43 PM Saurabh Saraswat > <saurabh.saras...@tcs.com.invalid> wrote: > > > > TCS Confidential > > > > Hi Kit, > > > > Thanks for your response. > > > > We intend to support this. What is the process to collaborate ? > > Is there a corporate CLA ? > > > > Is there any team, already working to make a kubernetes operator for it or > > we should take this trafficserver-ingress-controller > > <https://github.com/apache/trafficserver-ingress-controller> as base and > > start creating the operator ? > > > > regards, > > Saurabh > > > > ________________________________ > > From: Shu Kit Chan <chanshu...@gmail.com> > > Sent: Tuesday, July 1, 2025 21:13 > > To: dev@trafficserver.apache.org <dev@trafficserver.apache.org> > > Subject: Re: New Feature - Kubernetes Operator Creation > > > > External Email : Be cautious while opening any links or attachments. > > > > We do have an ingress controller here - > > https://github.com/apache/trafficserver-ingress-controller > > It is still experimental and obviously it is not yet made an operator. > > > > You are welcome to collaborate in that repository and work together > > there. Thanks. > > > > Kit > > > > On Mon, Jun 30, 2025 at 10:47 PM Saurabh Saraswat > > <saurabh.saras...@tcs.com.invalid> wrote: > > > > > > TCS Confidential > > > > > > Hi Traffic Server Team, > > > > > > We have noted that there is no operator for Apache Traffic Server, but it > > > can serve as a ingress controller in kubernetes. > > > Most of the other popular ingress controllers have it. With Operators > > > (and CRDs ) management of Traffic Server will be lot easier, standardized > > > and automated. > > > Adding a operator layer to the Apache Traffic Server, has it been > > > discussed/considered internally ? > > > > > > Let us know your thoughts on this. > > > If this mail should have been sent to any other address, please let me > > > know. > > > > > > > > > Thank you. > > > regards, > > > Saurabh > > > =====-----=====-----===== > > > Notice: The information contained in this e-mail > > > message and/or attachments to it may contain > > > confidential or privileged information. If you are > > > not the intended recipient, any dissemination, use, > > > review, distribution, printing or copying of the > > > information contained in this e-mail message > > > and/or attachments to it are strictly prohibited. If > > > you have received this communication in error, > > > please notify us by reply e-mail or telephone and > > > immediately and permanently delete the message > > > and any attachments. Thank you > > > > > >
