-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Logging Bucket #454
Comments
Hi @evgenybenchsci, thanks for your resource request. We have this resource in our queue and might have it supported by June. We will update this thread for more information and updates. |
Hi @caieo Thanks for the prompt response. |
Hi, is there a timeline for LoggingBucket already? Thanks in advance! |
Hi @cNULLde, unfortunately our original timeline was pushed back. Our current ETA for this resource is now hopefully near the end of Q3. We'll post future updates in this thread. |
Any updates on this? |
Hi @RenePinnow, sorry for the delay, but due to some blockers and limited bandwidth on our team, the ETA on this resource was pushed back again. We'll be hoping to have it supported by 2022 Q1. If this timeline does not work out for you, you can raise the priority by filing an issue with GCP support, where we can get some more info to reprioritize it. |
@caieo |
@mbzomowski |
Hi @RenePinnow we are still tracking this, sorry for the delay. No updates as of yet, but it now looks like this functionality will be added in Q2. |
This is added in v1.80.0. Note that only https://github.com/GoogleCloudPlatform/k8s-config-connector/releases/tag/v1.80.0 |
To allow the use of LoggingLogSink with Logging Bucket it would be great to add support for Logging Bucket resource. It looks like the required functionality already supported by Terraform. Since there are several types of Logging Buckets, the preference is for the project-level bucket.
Currently, ConfigConnector does not allow configuring LogSink with LogBucket, so we will need to manage it manually (or using scripts).
The text was updated successfully, but these errors were encountered: