SamWheating opened a new pull request, #53983:
URL: https://github.com/apache/airflow/pull/53983

   <!--
    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at
   
      http://www.apache.org/licenses/LICENSE-2.0
   
    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.
    -->
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   We have been using multiple kubernetes schedulers in order to improve the 
autoscaling performance of our clusters. This includes using separate 
schedulers for evictable pods (such as the airflow scheduler or webserver) and 
non-evictable pods (such as spark drivers or Airflow kubernetesExecutor pods). 
   
   Currently the Airflow helm chart allows us to set the schedulerName (added 
in https://github.com/apache/airflow/pull/33843) but this can only be set 
globally across all airflow components. We would like to override this for only 
the workers, similar to how other fields such as node selectors and affinity 
can be overridden. 
   
   We could also support configuring an overriding schedulerName for all other 
components (webserver, scheduler, etc) but I can't think of any need for this 
currently.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to