# experiments core class
import tigercontrol
from tigercontrol.experiments import metrics as metrics_module
from tigercontrol import error
import jax.numpy as np
from tigercontrol.environments.time_series import TimeSeriesEnvironment
from tigercontrol.controllers.time_series import TimeSeriesController
from tigercontrol.utils.random import set_key
from tqdm import tqdm
import inspect
import time
############## TO MAKE AUTOMATIC !!! #################
metrics = {'mse': metrics_module.mse, 'cross_entropy': metrics_module.cross_entropy}
def to_dict(x):
'''
Description: If x is not a dictionary, transforms it to one by assigning None values to entries of x;
otherwise, returns x.
Args:
x (dict / list): either a dictionary or a list of keys for the dictionary
Returns:
A dictionary 'version' of x
'''
if(x is None):
return {}
elif(type(x) is not dict):
x_dict = {}
for key in x:
x_dict[key] = [(key, None)]
return x_dict
else:
return x
def get_ids(x):
'''
Description: Gets the ids of environments/controllers
Args:
x (list / dict): list of ids of environments/controllers or dictionary of environments/controllers and parameters
Returns:
x (list): list of environment/controllers ids
'''
if(type(x) is dict):
ids = []
for main_id in x.keys():
for (custom_id, _) in x[main_id]:
ids.append(custom_id)
return ids
else:
return x
[docs]def create_full_environment_to_controllers(environments_ids, controller_ids):
'''
Description: Associate all given environments to all given controllers.
Args:
environment_ids (list): list of environment names
controller_ids (list): list of controller names
Returns:
full_environment_to_controllers (dict): association environment -> controller
'''
full_environment_to_controllers = {}
for environment_id in environments_ids:
full_environment_to_controllers[environment_id] = []
for controller_id in controller_ids:
full_environment_to_controllers[environment_id].append(controller_id)
return full_environment_to_controllers
##### CURRENTLY ONLY WORKS WITH TIME SERIES #######
[docs]def run_experiment(environment, controller, metric = 'mse', key = 0, timesteps = 100, verbose = True, load_bar = True):
'''
Description: Initializes the experiment instance.
Args:
environment (tuple): environment id and parameters to initialize the specific environment instance with
controller (tuple): controller id and parameters to initialize the specific controller instance with
metric (string): metric we are interesting in computing for current experiment
key (int): for reproducibility
timesteps(int): number of time steps to run experiment for
Returns:
loss (list): loss series for the specified metric over the entirety of the experiment
time (float): time elapsed
memory (float): memory used
'''
set_key(key)
# extract specifications
(environment_id, environment_params) = environment
(controller_id, controller_params) = controller
loss_fn = metrics[metric]
# initialize environment
environment = tigercontrol.environment(environment_id)
if(environment_params is None):
init = environment.initialize()
else:
init = environment.initialize(**environment_params)
# get first x and y
if(environment.has_regressors):
x, y = init
else:
x, y = init, environment.step()
# initialize controller
controller = tigercontrol.controller(controller_id)
if(controller_params is None):
controller.initialize()
else:
controller.initialize(**controller_params)
'''if(environment.has_regressors and not controller.uses_regressors):
print("ERROR: %s has regressors but %s only uses output signal." % (environment_id, controller_id))
return np.zeros(timesteps), 0.0, 0.0'''
if(controller.compatibles.isdisjoint(environment.compatibles)):
print("ERROR: %s and %s are incompatible!" % (environment_id, controller_id))
return np.zeros(timesteps), 0.0, 0.0
if(verbose):
print("Running %s on %s..." % (controller_id, environment_id))
loss = []
time_start = time.time()
memory = 0
# get loss series
for i in tqdm(range(timesteps), disable = (not load_bar)):
# get loss and update controller
cur_loss = float(loss_fn(y, controller.predict(x)))
loss.append(cur_loss)
controller.update(y)
# get new pair of observation and label
new = environment.step()
if(environment.has_regressors):
x, y = new
else:
x, y = y, new
return np.array(loss), time.time() - time_start, memory


else:
expand_batch_x = torch.full(size=(B, k, D), fill_value=fill_value)
expand_batch_x[:, :N, :] = batch_x
batch_x = expand_batch_x.contiguous()
batch_x[batch_x == fill_value] = 0
x = batch_x.view(B, k * D)
batch_x = batch_x[:, :k].contiguous()
else:
expand_batch_x = batch_x.new_full((B, k - N, D), fill_value)
batch_x = torch.cat([batch_x, expand_batch_x], dim=1)
batch_x[batch_x == fill_value] = 0
x = batch_x.view(B, k * D)


A preeminent scientist -- and the world's most prominent atheist -- asserts the irrationality of belief in God and the grievous harm religion has inflicted on society, from the Crusades to 9/11.
With rigor and wit, Dawkins examines God in all his forms, from the sex-obsessed tyrant of the Old Testament to the more benign (but still illogical) Celestial Watchmaker favored by some Enlightenment thinkers. He eviscerates the major arguments for religion and demonstrates the supreme improbability of a supreme being. He shows how religion fuels war, foments bigotry, and abuses children, buttressing his points with historical and contemporary evidence. The God Delusion makes a compelling case that belief in God is not just wrong but potentially deadly. It also offers exhilarating insight into the advantages of atheism to the individual and society, not the least of which is a clearer, truer appreciation of the universe's wonders than any faith could ever muster.
The boy lay prone in the grass, his chin resting on his hands. He suddenly found himself overwhelmed by a heightened awareness of the tangled stems and roots, a forest in microcosm, a transfigured world of ants and beetles and even - though he wouldn't have known the details at the time - of soil bacteria by the billions, silently and invisibly shoring up the economy of the micro-world. Suddenly the micro-forest of the turf seemed to swell and become one with the universe, and with the rapt mind of the boy contemplating it. He interpreted the experience in religious terms and it led him eventually to the priesthood. He was ordained an Anglican priest and became a chaplain at my school, a teacher of whom I was fond. It is thanks to decent liberal clergymen like him that nobody could ever claim that I had religion forced down my throat.


You think you have a good deal of general awareness with a tinge of Civil engineering cognizance?You get awestruck by the amazing things around you, appreciating the greatness in them? Enthusiastic about the reasons and explanations?
Well then, CEA QUIZ is the right place for you.  Showing your calibre win some handsome prizes. Quizzing happens through a varied levels and themes giving you loads of fun and excitement. CEA quiz touches upon various fields of Civil Engineering.
The paradox in CEA is that it teaches you more than it tests you.
Learn the unlearnt!
CEA Quiz encourages Learning.
CEA Quiz is an on spot registered event. It consists of three rounds.
Note:
Anyone who is love to rack their brains and learn something new and interesting can participate.
No, the registration is onspot.
Teams of three or less members.
Sure you can. CEA Quiz is open to everyone.
No, they can be from different colleges.
You need to register at the hospitality desk of CEA fest'15 few hours before the start of the event.
Just your enthusiasm and open brains. Stationary will be provided at the event.
You can always contact the event Coordinators for any queries whose contact details are provided in the tab'Contact Us' in the website.
For any queries regarding the Event kindly mail us or contact us at given details.
Event Email id-<EMAIL_ADDRESS>Coordinator Details-
Shanmukha Surya Teja
+91<PHONE_NUMBER>
<EMAIL_ADDRESS>Hemasree
+91<PHONE_NUMBER>
<EMAIL_ADDRESS>You can’t build a great building on a weak foundation.
You must have a solid foundation if you are going to have a strong superstructure.Foundation is the base of any structure. Without a firm foundation, the structure cannot stand. The strength of the foundation determines the life of structure. The design of foundation depends on soil and load. There has been a surge of infrastructural development in India during the last few years. High rise buildings have become nations’ symbol of pride and development. The foundation design is what matters. Hence it is a big challenge for us civil engineers to design a foundation for a high rise building in Indian conditions.
The participants are required to design a foundation for a high rise building, ensuring that it can stand the test of time.
It should be noted that the foundation design should not only bear the load of the building but also be cost efficient.
The participating teams should make a presentation giving their analysis, approach and factors considered in designing the foundation, along with the technical details of the foundation. The participants are required to devise innovative techniques to build the foundation of a building with given specifications.
Find the problem statement here.
For any queries or issues feel free to drop a mail at<EMAIL_ADDRESS>or to contact us :)
Note: It is recommended to include all these points in detail in your presentation, justifying your design to stand a better chance of winning.
The TDP should contain a short description of your approach to the problem statement with a maximum word limit of 500, the details of your team with each members name,e-mail id, contact number,college.
Send it before 1st March 2015 in pdf format.
Anyone who is interested and enthusiastic to show out his true potential to all and learn something new and interesting can participate
Yes it is.
Teams of 3 members(maximum).
Geo Genius is open to all.
No, they can be from different colleges.
You need to register by sending TDP at<EMAIL_ADDRESS>Just your enthusiasm and your presentation , all else required will be provided on spot.
You can always contact the event Coordinators for any queries whose contact details are provided in the CONTACTS(put a link to it maybe) in this website.
Please refer to the hospitality tab in the website.
No,only the students of a college or University can participate.
No, not at all. Participants can be from any branch.
Have you got a zeal and dedication to the environment and our water resources?CEA FEST 2015 presents to you Aquanomics- a brain twisting event from the Department of Environmental and Water Resources Engineering.
This event would provide you with a rare opportunity of an experience with environmental and water resources engineering.It prepares you for the growing demand of green buildings in the future.
It is a pre-registered event on environmental engineering.
Aquanomics begins its journey with an event that integrates water filtration and irrigation.Both the parts would have equal weightage.
The filtered water should follow the Bureau of Indian Standards for irrigation purpose. The soil type should be taken as that for Chennai, that is, mostly clayey soil for semi-tolerant crops.
Please find the updated problem statement attached here.
The last date for TDP submission is 21st February 2015.
The TDP should also contain names of all the members, their respective colleges, email ids and college ids.
Email id<EMAIL_ADDRESS>Swarnima:
Mobile number: +91<PHONE_NUMBER>
Email<EMAIL_ADDRESS>Akhila Chowdary:
Mobile number: +91<PHONE_NUMBER>
Email<EMAIL_ADDRESS>It is a pre-registered team event. Each team should have 3 members.
The event will have two rounds. The results of the first part would be used in the second part.
Both parts will be given equal weight age in terms of scoring.
The first part will pertain more to Environmental Engineering and the second part towards Water Resources Engineering.
Materials for the first part of the event should be brought by the participants and those for the second part would be provided.
No, it is not necessary.
Yes, the material for the first part of the event has to be brought by you. Materials for the second part would be provided at the event.
To register for the event, the participant teams must send a TDP to the mail id for the event given in the Contacts Tab.
No, the event has no pre-requisites.
For the first part of the event following are the criteria in order of priority:
The world is getting automated and so should we, want to showcase your creative skills in software?
Here is a CAD Competition where students gets an opportunity to test their planning skills, level in functionality of building and time management. This event would be just right to showcase your talents. Unveil your expertise in AutoCAD by proving yourself in the areas of drafting and more!
Unleash your innovative skills to shape the future!!
Email id<EMAIL_ADDRESS>Contact nos.
Harshini: +919043255388
Poojan : +919884180125
Cad contest is an on spot event. Participants are required to get themselves registered in teams of two at the hospitality desk during the fest. Only 40 teams will be allowed to participate in competition. Those 40 teams are taken based on “first come first serve” basis. The problem statement will be provided and the time allotted for it will be intimated on the day of the event. All the required material will be provided during the event.
Yes, it is open to all students from all departments
You have to register at the hospitality desk on the day of the event.
Team consists of 2 members.
Yes, group members can be of different colleges.
Yes. Anyone who has knowledge of CAD may participate.
No, whatever is required will be provided by us.
Time allotted will be intimated on the day of the event.
You can always contact the event Coordinators for any queries whose contact details are provided in the tab ‘CONTACTS’ in this website.
Concrete is as we know the heart of modern day construction. For a commoner, civil engineering means concrete. Its unique features make it the best choice as a material. Many people think all concrete is the same. This is not true! Concrete is no longer a simple grey mass, but it has made its way to become pervious (lighter with honey comb structures), more beautiful (architectural concrete), colored, stronger (high strength concrete), self-compacting to name a few.
Today in India, we see that in cities, storm-water runoff is a big challenge during monsoon. Storm water runoff increases both erosion and flooding influencing both water quality and quantity problems. A simple solution to avoiding these problems is to stop installing the impervious surfaces that block natural water infiltration into the soil. Rather than building them with conventional concrete or asphalt, more and more communities, municipalities, and businesses are switching to pervious concrete or porous pavement, a material that offers the inherent durability and low life-cycle costs of a typical concrete pavement while retaining storm water runoff and replenishing local watershed systems. Already one of the most happening topics in Research & Development, pervious concrete is rapidly gaining popularity in the industrial sector as well. CEA Fest’s Concrete Challenge offers the right platform to solve this problem from this aspect.
Concrete challenge returns this year with a problem statement that demands participants to design such pervious concrete mix which satisfies required strength and permeability requirements as well as is lightweight because of the abundance of pores. Achieving this through thorough research and presenting it to win the judges over is the ‘challenge’ Concrete Challenge has to offer you.
To make two 100x150 mm (diameter 100mm, length 150mm) pervious concrete cylinders having
Find the problem statement here.
Last day to register – 28/02/2015
TDP submission last date – 01/03/2015
Declaration of finalists – 05/03/2015
Casting of the sample – 06/03/2015
Report submission - 09/03/2015
Evaluation – 14/03/2015
Email id<EMAIL_ADDRESS>Contact nos.
SHUBHAM SARWADE: +91<PHONE_NUMBER>
CH.VENKATESH : +91<PHONE_NUMBER>
The event is of ‘preregistered’ category.
Participation :
Evaluation of each team will be done in two parts.
The team has to prepare an A3 size poster with details such as details regarding the mix design and related research done by them and present it to the judges. The poster will be judged on basis of the content, presentation skills and the poster design. This will be graded out of 10.
The report will be graded by the event coordinators out of 10. The report should be submitted through email before 9th March.
Stay tuned for some excited prizes.
Yes, it is.
The team should have a maximum of 4 members.
Any individual pursuing a degree in Civil Engineering from a Government of India recognized college will be able to participate.
Not necessary.
You will be disqualified.
Online, for further details refer to the Registration tab.
Yes. For further details refer to the Hospitality tab.
Concerned professor.
You can always contact the event coordinators for any queries whose contact are provided in the tab ‘CONTACTS’ in this website.
Have you ever felt that Civil Engineering jobs pay no respect to ethics? Have you ever had differing views regarding the building of dams and its purpose? Do you feel the constant urge to question the world's "misconceived opinions"? If so, come and be a part of the CEA Debate, an event that brings together students from across India to gather their thoughts, re-interpret facts and kindle thought on a wide variety of issues and problems concerning Civil Engineering and its practice around the world.
Battle out your differences in teams of two against students from various institutes on trending topics, with professors presiding over as judges. After all, "Time spent arguing is, oddly enough, almost never wasted".
Email id<EMAIL_ADDRESS>Contact nos.
Ananth Sundararaman - +91<PHONE_NUMBER>
The format going to be followed is Public Forum debate (if you don’t know about the format then here you go)
Format for Public Forum Debate (This will be followed strictly adhered to.) All rounds will be 2 minutes each unless mentioned otherwise.
| Event | Duration |
|---|---|
| First “For” Constructive Speaker- | 2 minutes |
| First “Against” Constructive Speaker- | 2 minutes |
| Second “For” Constructive Speaker- | 2 minutes |
| Second “Against” Constructive Speaker- | 2 minutes |
| Rebuttal by First Speaker "for"- | 3 minutes |
| Proposition Rebuttal by First Speaker- | 3 minutes |
The schedule of debates between teams and the day of each debate will be decided on the spot after determining the number of participants.Topics to be released on 28th February
Experience serves not only to confirm theory, but differs from it without disturbing it, it leads to new truths which theory only has not been able to reach.
-D'Alembert
Aiming to be one of those master minds in designing? You have been designing various structures in different software but not by real life materials so here is the chance to prove your skills. Here comes the new edition of Master Builder to put one's brain cells to thought with a challenge to build amazing structures. This event throws a real life problem to civil engineering aspirants. With its challenging problem statement master builder is sure to attract attention of one and all.
Master builder in this coming year brings you a unique problem statement. Movable bridges are one of the most interesting civil structures. Well now it’s time to build it on our own. The participants are challenged to build a movable bridge, a bridge that can open up whenever required. Seems interesting, doesn’t it?
The problem statement can be found here.
Last date to submit report : 21-02-2015
Announcement of finalists : 27-02-2015
Final Presentations : During CEA fest
Email id<EMAIL_ADDRESS>Contact nos.
Vivek T : +91<PHONE_NUMBER>
Kiran Ande: +91<PHONE_NUMBER>
TDP has to be submitted by 21st February. The TDP can be found here.
A team can consist of 4 members.
Anyone can participate irrespective of their branch and year.
No, they can be from different colleges.
It is pre-registered event; the process for registration is given in FORMAT tab.
No, none are required.
Yes, please refer to the hospitality tab in the website.
You can always contact the event coordinators for any queries whose contact are provided in the tab ‘CONTACTS’ in this website.
The first word that one thinks of when one hears “Civil Engineering” is ‘build’!
The most popular, enthralling and alluring event in the CEA Fest is ‘Modelling’. It provides an apt platform for budding civil engineers to showcase their engineering skills.
Avail yourselves this challenging hands-on event wherein you get to design and build a model according to the riveting problem statement given, with simple materials like ice cream sticks, twine, newspaper, straws and other likewise materials.
Get ready to discover the creative genius in you by being a part of the largest participated event in the CEA Fest!
Modelling, in the coming edition of CEA Fest, promises to bring to you an off-centre problem statement which would be given at the venue itself as it is an on-spot event.
Last date to submit report : 21-02-2015
Announcement of finalists : 27-02-2015
Final Presentations : During CEA fest
Email id<EMAIL_ADDRESS>Contact nos.
SAMHITA MANGU : +91 99402 47348
SNEHASAGAR : +91 90032 95682
Modelling is an on spot event. It has only one round. Participants are required to get themselves registered in teams of three at the hospitality desk in time. The problem statement and the required material would be provided. Participants are required to make the model according to the problem statement with the material provided by us in 3hrs time.
A team can consist of 3 members.
Anyone can participate irrespective of their branch and year.
No, all the things you need for the event will be provided to you.
No, they can be from different colleges.
You should register at the hospitality desk few hours before the starting of the event.
No, testing will take place on the next day in the presence of the participants, under the supervision of the professor.
No, none are required.
You can always contact the event coordinators for any queries whose contact are provided in the tab ‘CONTACTS’ in this website.
"Take away paradox from the thinker and you have a professor."
Civil Engineering association CEA presents in pure form and with challenging spirit an event, POTENTIAL PROFESSOR. Potential Professor provides a platform to showcase immense talent and potential in you to become a future professor and to become the source of knowledge for others in the future.
In the class rooms, ever felt that you could explain better than what the professor is teaching? Do you think that Indian teaching system should be changed? Should be more interactive and fun? Stage is yours. Let’s roll the dice with your potential.
The event will test the teaching skills in you and how much better you can make the audience learn about the topic that you are explaining. Event will be judged by the elite faculty of Civil Engineering Department, IIT Madras. Participate to win the tag “THE BEST POTENTIAL PROFESSOR, CEA, IIT MADRAS.”
Submit the answers for the Questions for Registration via Email-
Questions for Registration:
Compulsory Question –
Second Question (Sub-Department Choice Question) -
Choose a topic from the respective Sub department and Prepare for the final show off. List of topics will be provided to the shortlisted participants.
The deadline for submitting the answers will be 22-02-2015. (Sunday)
Announcement of the finalist students will be done on 25-02-15. (Wednesday)
Around 25-30 participants will be shortlisted for the final round. (Approximately 5-6 participants from each sub-department)
On the same day (25.02.15) after announcing the finalists the topics for the final round of event will be announced to the entire finalists. There will be 2-3 topics from each sub-department and overall 10-12 topics will be there from which participants have to choose one topic (From their interested sub-department which they already mentioned during registration.)
Finalized Participants have to give their chosen topic through mail (*only topic name) to the coordinators before 02-03-2015 (Monday) which will indeed fix their confirmation for the event.
(*Strictly participants cannot change their sub-department after getting finalized for the final round.)
Email id<EMAIL_ADDRESS>Ramya Desineedi
+919884180556
<EMAIL_ADDRESS>Rahul Sakhare
+919043244545
<EMAIL_ADDRESS>Participants have to choose their field of interest. Second question will test one’s explaining skills in his/her own words. (*Answer limit -Maximum 500 words.)
Plagiarism will result in disqualification.
You will be shortlisted for the final round of the event depending on your views and answers and you will get chance to present yourself in Final Round Potential Professor: War of words, CEA, IIT Madras.
The most effective teacher with interesting teaching techniques gets the tag of “THE BEST POTENTIAL PROFESSOR, CEA, IIT MADRAS” along with the exiting prizes.
The judging will be done by the panel of Professors of IIT Madras and percentage votes of the students present in the class during the event.
The judge panel will judge the participants based on their communication skills, body language, spontaneity, planning and sequencing of the class, ability to create interaction in the class, the quantity and quality of content.
Weightage-
Anyone who is interested in teaching can participate in this event, irrespective of sub department of Civil Engineering and year.
Yes, it is pre-registered.
No, only one person can participate.
You need to answer the Registration questions and send the PDF to event email id-<EMAIL_ADDRESS>along with your personal details before 22-02-2015 (Sunday 12pm).
25-02-2015(Wednesday).
Yes, topics for finalists are released before and participant needs to give their chosen topic via email before 02-03-2015(Monday).
Anything you think is important while teaching a topic (for demonstration etc...)
You can always contact the event coordinators for any queries whose contact are provided in the tab ‘CONTACTS’ in this website.
ACT RESPONSIBLE, THINK SUSTAINABLE
The Earth’s ecosystems are now at a critical stage due to urbanization. Buildings and construction works have the largest single share in global resource use and pollution emission.
“What is the use of a house if you don’t have a decent planet to put it on?”
-Henry David Thoreau.
Sustainable designs are scientific attempts in order to protect the gifted planet. SUSTAINABLE DESIGN CHALLENGE acts as a platform to showcase ones designing skills, to model energy efficient buildings and infrastructure. So, here is an opportunity to think out of the box, design greener and compete with great minds.
Past editions of CEA fest have provided an opportunity to the students to showcase their skills in modelling energy efficient buildings. This year we are ready with another intriguing problem statement that challenges your perception, the DESIGN OF SMART CITY, the vision of government of India.
The constraint to modify the existing plan and design rekindles your thirst for knowledge and prompts you to understand the core of civil engineering in a revitalizing way.
Please find the problem statement here.
Last date to submit report : 28-02-2015
Announcement of finalists : 06-03-2015
Final Presentations : During CEA fest
Email id<EMAIL_ADDRESS>Contact nos.
Bhavitha –<PHONE_NUMBER>
Sashi Sekhar -<PHONE_NUMBER>
Maximum five members per team are allowed
Yes, proper certificate is to be presented.
At least one of the team members should be from civil.
There will NOT be any extension.
Please refer to the hospitality tab in the website.
No, Only the students of a college or University can participate.
CEA online quiz to challenge your brain and test your core knowledge ,understanding and speed.
A perfect platform to compete,verify and enhance your technical expertise in the field of Civil engineering.
CEA Online Quiz is a regular individual quizzing event. It is held on two days Online Quiz 1 : February 5th Online Quiz 2 : February 20th
CEA Online Wildcard Quiz is special event with Team participation of 3 or less. It is special because the top 10% of the winners of the "Wildcard online quiz" gets wild card entry directly to Round 2 of CEA Quiz which will happen on Day2 of CEA fest Online Wild card Quiz : March 7th Mark your calendars
Learn the unlearnt!
CEA Quiz encourages learning!
Hemasree :<PHONE_NUMBER><EMAIL_ADDRESS>Shanmukh:<PHONE_NUMBER><EMAIL_ADDRESS>Email ID<EMAIL_ADDRESS>Portal is open from 7pm - 9pm
Quiz is for 20 minutes with 25 MCQ's
No negative scores.
Prizes at stake!
No, they are both completely different.
CEA Online Quiz is an individual event, whereas, CEA Online Wildcard Quiz is a team of 3 or less event
Winning the online quiz "Wildcard Online Quiz" only will get you the wildcard entry.
The first Online Quiz is closed, please stay tuned for the next one on 20th February, 2015.


KubeControllerManagerConfiguration contains elements describing kube-controller manager.
| Field | Description |
|---|---|
apiVersion string |
kubecontrollermanager.config.k8s.io/v1alpha1 |
kind string |
KubeControllerManagerConfiguration |
Generic
*
GenericControllerManagerConfiguration
|
Generic holds configuration for a generic controller-manager |
KubeCloudShared
*
KubeCloudSharedConfiguration
|
KubeCloudSharedConfiguration holds configuration for shared related features both in cloud controller manager and kube-controller manager. |
AttachDetachController
*
AttachDetachControllerConfiguration
|
AttachDetachControllerConfiguration holds configuration for AttachDetachController related features. |
CSRSigningController
*
CSRSigningControllerConfiguration
|
CSRSigningControllerConfiguration holds configuration for CSRSigningController related features. |
DaemonSetController
*
DaemonSetControllerConfiguration
|
DaemonSetControllerConfiguration holds configuration for DaemonSetController related features. |
DeploymentController
*
DeploymentControllerConfiguration
|
DeploymentControllerConfiguration holds configuration for DeploymentController related features. |
StatefulSetController
*
StatefulSetControllerConfiguration
|
StatefulSetControllerConfiguration holds configuration for StatefulSetController related features. |
DeprecatedController
*
DeprecatedControllerConfiguration
|
DeprecatedControllerConfiguration holds configuration for some deprecated features. |
EndpointController
*
EndpointControllerConfiguration
|
EndpointControllerConfiguration holds configuration for EndpointController related features. |
EndpointSliceController
*
EndpointSliceControllerConfiguration
|
EndpointSliceControllerConfiguration holds configuration for EndpointSliceController related features. |
EndpointSliceMirroringController
*
EndpointSliceMirroringControllerConfiguration
|
EndpointSliceMirroringControllerConfiguration holds configuration for EndpointSliceMirroringController related features. |
EphemeralVolumeController
*
EphemeralVolumeControllerConfiguration
|
EphemeralVolumeControllerConfiguration holds configuration for EphemeralVolumeController related features. |
GarbageCollectorController
*
GarbageCollectorControllerConfiguration
|
GarbageCollectorControllerConfiguration holds configuration for GarbageCollectorController related features. |
HPAController
*
HPAControllerConfiguration
|
HPAControllerConfiguration holds configuration for HPAController related features. |
JobController
*
JobControllerConfiguration
|
JobControllerConfiguration holds configuration for JobController related features. |
CronJobController
*
CronJobControllerConfiguration
|
CronJobControllerConfiguration holds configuration for CronJobController related features. |
NamespaceController
*
NamespaceControllerConfiguration
|
NamespaceControllerConfiguration holds configuration for NamespaceController related features. NamespaceControllerConfiguration holds configuration for NamespaceController related features. |
NodeIPAMController
*
NodeIPAMControllerConfiguration
|
NodeIPAMControllerConfiguration holds configuration for NodeIPAMController related features. |
NodeLifecycleController
*
NodeLifecycleControllerConfiguration
|
NodeLifecycleControllerConfiguration holds configuration for NodeLifecycleController related features. |
PersistentVolumeBinderController
*
PersistentVolumeBinderControllerConfiguration
|
PersistentVolumeBinderControllerConfiguration holds configuration for PersistentVolumeBinderController related features. |
PodGCController
*
PodGCControllerConfiguration
|
PodGCControllerConfiguration holds configuration for PodGCController related features. |
ReplicaSetController
*
ReplicaSetControllerConfiguration
|
ReplicaSetControllerConfiguration holds configuration for ReplicaSet related features. |
ReplicationController
*
ReplicationControllerConfiguration
|
ReplicationControllerConfiguration holds configuration for ReplicationController related features. |
ResourceQuotaController
*
ResourceQuotaControllerConfiguration
|
ResourceQuotaControllerConfiguration holds configuration for ResourceQuotaController related features. |
SAController
*
SAControllerConfiguration
|
SAControllerConfiguration holds configuration for ServiceAccountController related features. |
ServiceController
*
ServiceControllerConfiguration
|
ServiceControllerConfiguration holds configuration for ServiceController related features. |
TTLAfterFinishedController
*
TTLAfterFinishedControllerConfiguration
|
TTLAfterFinishedControllerConfiguration holds configuration for TTLAfterFinishedController related features. |
(Appears in: KubeControllerManagerConfiguration)
AttachDetachControllerConfiguration contains elements describing AttachDetachController.
| Field | Description |
|---|---|
DisableAttachDetachReconcilerSync
*
bool
|
Reconciler runs a periodic loop to reconcile the desired state of the with the actual state of the world by triggering attach detach operations. This flag enables or disables reconcile. Is false by default, and thus enabled. |
ReconcilerSyncLoopPeriod
*
meta/v1.Duration
|
ReconcilerSyncLoopPeriod is the amount of time the reconciler sync states loop wait between successive executions. Is set to 5 sec by default. |
(Appears in: CSRSigningControllerConfiguration)
CSRSigningConfiguration holds information about a particular CSR signer
| Field | Description |
|---|---|
CertFile
*
string
|
certFile is the filename containing a PEM-encoded X509 CA certificate used to issue certificates |
KeyFile
*
string
|
keyFile is the filename containing a PEM-encoded RSA or ECDSA private key used to issue certificates |
(Appears in: KubeControllerManagerConfiguration)
CSRSigningControllerConfiguration contains elements describing CSRSigningController.
| Field | Description |
|---|---|
ClusterSigningCertFile
*
string
|
clusterSigningCertFile is the filename containing a PEM-encoded X509 CA certificate used to issue cluster-scoped certificates |
ClusterSigningKeyFile
*
string
|
clusterSigningCertFile is the filename containing a PEM-encoded RSA or ECDSA private key used to issue cluster-scoped certificates |
KubeletServingSignerConfiguration
*
CSRSigningConfiguration
|
kubeletServingSignerConfiguration holds the certificate and key used to issue certificates for the kubernetes.io/kubelet-serving signer |
KubeletClientSignerConfiguration
*
CSRSigningConfiguration
|
kubeletClientSignerConfiguration holds the certificate and key used to issue certificates for the kubernetes.io/kube-apiserver-client-kubelet |
KubeAPIServerClientSignerConfiguration
*
CSRSigningConfiguration
|
kubeAPIServerClientSignerConfiguration holds the certificate and key used to issue certificates for the kubernetes.io/kube-apiserver-client |
LegacyUnknownSignerConfiguration
*
CSRSigningConfiguration
|
legacyUnknownSignerConfiguration holds the certificate and key used to issue certificates for the kubernetes.io/legacy-unknown |
ClusterSigningDuration
*
meta/v1.Duration
|
clusterSigningDuration is the max length of duration signed certificates will be given. Individual CSRs may request shorter certs by setting spec.expirationSeconds. |
(Appears in: KubeControllerManagerConfiguration)
CronJobControllerConfiguration contains elements describing CrongJob2Controller.
| Field | Description |
|---|---|
ConcurrentCronJobSyncs
*
int32
|
concurrentCronJobSyncs is the number of job objects that are allowed to sync concurrently. Larger number = more responsive jobs, but more CPU (and network) load. |
(Appears in: KubeControllerManagerConfiguration)
DaemonSetControllerConfiguration contains elements describing DaemonSetController.
| Field | Description |
|---|---|
ConcurrentDaemonSetSyncs
*
int32
|
concurrentDaemonSetSyncs is the number of daemonset objects that are allowed to sync concurrently. Larger number = more responsive daemonset, but more CPU (and network) load. |
(Appears in: KubeControllerManagerConfiguration)
DeploymentControllerConfiguration contains elements describing DeploymentController.
| Field | Description |
|---|---|
ConcurrentDeploymentSyncs
*
int32
|
concurrentDeploymentSyncs is the number of deployment objects that are allowed to sync concurrently. Larger number = more responsive deployments, but more CPU (and network) load. |
(Appears in: KubeControllerManagerConfiguration)
DeprecatedControllerConfiguration contains elements be deprecated.
(Appears in: KubeControllerManagerConfiguration)
EndpointControllerConfiguration contains elements describing EndpointController.
| Field | Description |
|---|---|
ConcurrentEndpointSyncs
*
int32
|
concurrentEndpointSyncs is the number of endpoint syncing operations that will be done concurrently. Larger number = faster endpoint updating, but more CPU (and network) load. |
EndpointUpdatesBatchPeriod
*
meta/v1.Duration
|
EndpointUpdatesBatchPeriod describes the length of endpoint updates batching period. Processing of pod changes will be delayed by this duration to join them with potential upcoming updates and reduce the overall number of endpoints updates. |
(Appears in: KubeControllerManagerConfiguration)
EndpointSliceControllerConfiguration contains elements describing EndpointSliceController.
| Field | Description |
|---|---|
ConcurrentServiceEndpointSyncs
*
int32
|
concurrentServiceEndpointSyncs is the number of service endpoint syncing operations that will be done concurrently. Larger number = faster endpoint slice updating, but more CPU (and network) load. |
MaxEndpointsPerSlice
*
int32
|
maxEndpointsPerSlice is the maximum number of endpoints that will be added to an EndpointSlice. More endpoints per slice will result in fewer and larger endpoint slices, but larger resources. |
EndpointUpdatesBatchPeriod
*
meta/v1.Duration
|
EndpointUpdatesBatchPeriod describes the length of endpoint updates batching period. Processing of pod changes will be delayed by this duration to join them with potential upcoming updates and reduce the overall number of endpoints updates. |
(Appears in: KubeControllerManagerConfiguration)
EndpointSliceMirroringControllerConfiguration contains elements describing EndpointSliceMirroringController.
| Field | Description |
|---|---|
MirroringConcurrentServiceEndpointSyncs
*
int32
|
mirroringConcurrentServiceEndpointSyncs is the number of service endpoint syncing operations that will be done concurrently. Larger number = faster endpoint slice updating, but more CPU (and network) load. |
MirroringMaxEndpointsPerSubset
*
int32
|
mirroringMaxEndpointsPerSubset is the maximum number of endpoints that will be mirrored to an EndpointSlice for an EndpointSubset. |
MirroringEndpointUpdatesBatchPeriod
*
meta/v1.Duration
|
mirroringEndpointUpdatesBatchPeriod can be used to batch EndpointSlice updates. All updates triggered by EndpointSlice changes will be delayed by up to 'mirroringEndpointUpdatesBatchPeriod'. If other addresses in the same Endpoints resource change in that period, they will be batched to a single EndpointSlice update. Default 0 value means that each Endpoints update triggers an EndpointSlice update. |
(Appears in: KubeControllerManagerConfiguration)
EphemeralVolumeControllerConfiguration contains elements describing EphemeralVolumeController.
| Field | Description |
|---|---|
ConcurrentEphemeralVolumeSyncs
*
int32
|
ConcurrentEphemeralVolumeSyncseSyncs is the number of ephemeral volume syncing operations that will be done concurrently. Larger number = faster ephemeral volume updating, but more CPU (and network) load. |
(Appears in: KubeControllerManagerConfiguration)
GarbageCollectorControllerConfiguration contains elements describing GarbageCollectorController.
| Field | Description |
|---|---|
EnableGarbageCollector
*
bool
|
enables the generic garbage collector. MUST be synced with the corresponding flag of the kube-apiserver. WARNING: the generic garbage collector is an alpha feature. |
ConcurrentGCSyncs
*
int32
|
concurrentGCSyncs is the number of garbage collector workers that are allowed to sync concurrently. |
GCIgnoredResources
*
[]GroupResource
|
gcIgnoredResources is the list of GroupResources that garbage collection should ignore. |
(Appears in: GarbageCollectorControllerConfiguration)
GroupResource describes an group resource.
| Field | Description |
|---|---|
Group
*
string
|
group is the group portion of the GroupResource. |
Resource
*
string
|
resource is the resource portion of the GroupResource. |
(Appears in: KubeControllerManagerConfiguration)
HPAControllerConfiguration contains elements describing HPAController.
| Field | Description |
|---|---|
ConcurrentHorizontalPodAutoscalerSyncs
*
int32
|
ConcurrentHorizontalPodAutoscalerSyncs is the number of HPA objects that are allowed to sync concurrently. Larger number = more responsive HPA processing, but more CPU (and network) load. |
HorizontalPodAutoscalerSyncPeriod
*
meta/v1.Duration
|
HorizontalPodAutoscalerSyncPeriod is the period for syncing the number of pods in horizontal pod autoscaler. |
HorizontalPodAutoscalerUpscaleForbiddenWindow
*
meta/v1.Duration
|
HorizontalPodAutoscalerUpscaleForbiddenWindow is a period after which next upscale allowed. |
HorizontalPodAutoscalerDownscaleStabilizationWindow
*
meta/v1.Duration
|
HorizontalPodAutoscalerDowncaleStabilizationWindow is a period for which autoscaler will look backwards and not scale down below any recommendation it made during that period. |
HorizontalPodAutoscalerDownscaleForbiddenWindow
*
meta/v1.Duration
|
HorizontalPodAutoscalerDownscaleForbiddenWindow is a period after which next downscale allowed. |
HorizontalPodAutoscalerTolerance
*
float64
|
HorizontalPodAutoscalerTolerance is the tolerance for when resource usage suggests upscaling/downscaling |
HorizontalPodAutoscalerCPUInitializationPeriod
*
meta/v1.Duration
|
HorizontalPodAutoscalerCPUInitializationPeriod is the period after pod start when CPU samples might be skipped. |
HorizontalPodAutoscalerInitialReadinessDelay
*
meta/v1.Duration
|
HorizontalPodAutoscalerInitialReadinessDelay is period after pod start during which readiness changes are treated as readiness being set for the first time. The only effect of this is that HPA will disregard CPU samples from unready pods that had last readiness change during that period. |
(Appears in: KubeControllerManagerConfiguration)
JobControllerConfiguration contains elements describing JobController.
| Field | Description |
|---|---|
ConcurrentJobSyncs
*
int32
|
concurrentJobSyncs is the number of job objects that are allowed to sync concurrently. Larger number = more responsive jobs, but more CPU (and network) load. |
(Appears in: KubeControllerManagerConfiguration)
NamespaceControllerConfiguration contains elements describing NamespaceController.
| Field | Description |
|---|---|
NamespaceSyncPeriod
*
meta/v1.Duration
|
namespaceSyncPeriod is the period for syncing namespace life-cycle updates. |
ConcurrentNamespaceSyncs
*
int32
|
concurrentNamespaceSyncs is the number of namespace objects that are allowed to sync concurrently. |
(Appears in: KubeControllerManagerConfiguration)
NodeIPAMControllerConfiguration contains elements describing NodeIpamController.
| Field | Description |
|---|---|
ServiceCIDR
*
string
|
serviceCIDR is CIDR Range for Services in cluster. |
SecondaryServiceCIDR
*
string
|
secondaryServiceCIDR is CIDR Range for Services in cluster. This is used in dual stack clusters. SecondaryServiceCIDR must be of different IP family than ServiceCIDR |
NodeCIDRMaskSize
*
int32
|
NodeCIDRMaskSize is the mask size for node cidr in cluster. |
NodeCIDRMaskSizeIPv4
*
int32
|
NodeCIDRMaskSizeIPv4 is the mask size for node cidr in dual-stack cluster. |
NodeCIDRMaskSizeIPv6
*
int32
|
NodeCIDRMaskSizeIPv6 is the mask size for node cidr in dual-stack cluster. |
(Appears in: KubeControllerManagerConfiguration)
NodeLifecycleControllerConfiguration contains elements describing NodeLifecycleController.
| Field | Description |
|---|---|
EnableTaintManager
*
bool
|
If set to true enables NoExecute Taints and will evict all not-tolerating Pod running on Nodes tainted with this kind of Taints. |
NodeEvictionRate
*
float32
|
nodeEvictionRate is the number of nodes per second on which pods are deleted in case of node failure when a zone is healthy |
SecondaryNodeEvictionRate
*
float32
|
secondaryNodeEvictionRate is the number of nodes per second on which pods are deleted in case of node failure when a zone is unhealthy |
NodeStartupGracePeriod
*
meta/v1.Duration
|
nodeStartupGracePeriod is the amount of time which we allow starting a node to be unresponsive before marking it unhealthy. |
NodeMonitorGracePeriod
*
meta/v1.Duration
|
nodeMontiorGracePeriod is the amount of time which we allow a running node to be unresponsive before marking it unhealthy. Must be N times more than kubelet's nodeStatusUpdateFrequency, where N means number of retries allowed for kubelet to post node status. |
PodEvictionTimeout
*
meta/v1.Duration
|
podEvictionTimeout is the grace period for deleting pods on failed nodes. |
LargeClusterSizeThreshold
*
int32
|
secondaryNodeEvictionRate is implicitly overridden to 0 for clusters smaller than or equal to largeClusterSizeThreshold |
UnhealthyZoneThreshold
*
float32
|
Zone is treated as unhealthy in nodeEvictionRate and secondaryNodeEvictionRate when at least unhealthyZoneThreshold (no less than 3) of Nodes in the zone are NotReady |
(Appears in: KubeControllerManagerConfiguration)
PersistentVolumeBinderControllerConfiguration contains elements describing PersistentVolumeBinderController.
| Field | Description |
|---|---|
PVClaimBinderSyncPeriod
*
meta/v1.Duration
|
pvClaimBinderSyncPeriod is the period for syncing persistent volumes and persistent volume claims. |
VolumeConfiguration
*
VolumeConfiguration
|
volumeConfiguration holds configuration for volume related features. |
VolumeHostCIDRDenylist
*
[]string
|
VolumeHostCIDRDenylist is a list of CIDRs that should not be reachable by the controller from plugins. |
VolumeHostAllowLocalLoopback
*
bool
|
VolumeHostAllowLocalLoopback indicates if local loopback hosts (<IP_ADDRESS>, etc) should be allowed from plugins. |
(Appears in: VolumeConfiguration)
PersistentVolumeRecyclerConfiguration contains elements describing persistent volume plugins.
| Field | Description |
|---|---|
MaximumRetry
*
int32
|
maximumRetry is number of retries the PV recycler will execute on failure to recycle PV. |
MinimumTimeoutNFS
*
int32
|
minimumTimeoutNFS is the minimum ActiveDeadlineSeconds to use for an NFS Recycler pod. |
PodTemplateFilePathNFS
*
string
|
podTemplateFilePathNFS is the file path to a pod definition used as a template for NFS persistent volume recycling |
IncrementTimeoutNFS
*
int32
|
incrementTimeoutNFS is the increment of time added per Gi to ActiveDeadlineSeconds for an NFS scrubber pod. |
PodTemplateFilePathHostPath
*
string
|
podTemplateFilePathHostPath is the file path to a pod definition used as a template for HostPath persistent volume recycling. This is for development and testing only and will not work in a multi-node cluster. |
MinimumTimeoutHostPath
*
int32
|
minimumTimeoutHostPath is the minimum ActiveDeadlineSeconds to use for a HostPath Recycler pod. This is for development and testing only and will not work in a multi-node cluster. |
IncrementTimeoutHostPath
*
int32
|
incrementTimeoutHostPath is the increment of time added per Gi to ActiveDeadlineSeconds for a HostPath scrubber pod. This is for development and testing only and will not work in a multi-node cluster. |
(Appears in: KubeControllerManagerConfiguration)
PodGCControllerConfiguration contains elements describing PodGCController.
| Field | Description |
|---|---|
TerminatedPodGCThreshold
*
int32
|
terminatedPodGCThreshold is the number of terminated pods that can exist before the terminated pod garbage collector starts deleting terminated pods. If <= 0, the terminated pod garbage collector is disabled. |
(Appears in: KubeControllerManagerConfiguration)
ReplicaSetControllerConfiguration contains elements describing ReplicaSetController.
| Field | Description |
|---|---|
ConcurrentRSSyncs
*
int32
|
concurrentRSSyncs is the number of replica sets that are allowed to sync concurrently. Larger number = more responsive replica management, but more CPU (and network) load. |
(Appears in: KubeControllerManagerConfiguration)
ReplicationControllerConfiguration contains elements describing ReplicationController.
| Field | Description |
|---|---|
ConcurrentRCSyncs
*
int32
|
concurrentRCSyncs is the number of replication controllers that are allowed to sync concurrently. Larger number = more responsive replica management, but more CPU (and network) load. |
(Appears in: KubeControllerManagerConfiguration)
ResourceQuotaControllerConfiguration contains elements describing ResourceQuotaController.
| Field | Description |
|---|---|
ResourceQuotaSyncPeriod
*
meta/v1.Duration
|
resourceQuotaSyncPeriod is the period for syncing quota usage status in the system. |
ConcurrentResourceQuotaSyncs
*
int32
|
concurrentResourceQuotaSyncs is the number of resource quotas that are allowed to sync concurrently. Larger number = more responsive quota management, but more CPU (and network) load. |
(Appears in: KubeControllerManagerConfiguration)
SAControllerConfiguration contains elements describing ServiceAccountController.
| Field | Description |
|---|---|
ServiceAccountKeyFile
*
string
|
serviceAccountKeyFile is the filename containing a PEM-encoded private RSA key used to sign service account tokens. |
ConcurrentSATokenSyncs
*
int32
|
concurrentSATokenSyncs is the number of service account token syncing operations that will be done concurrently. |
RootCAFile
*
string
|
rootCAFile is the root certificate authority will be included in service account's token secret. This must be a valid PEM-encoded CA bundle. |
(Appears in: KubeControllerManagerConfiguration)
StatefulSetControllerConfiguration contains elements describing StatefulSetController.
| Field | Description |
|---|---|
ConcurrentStatefulSetSyncs
*
int32
|
concurrentStatefulSetSyncs is the number of statefulset objects that are allowed to sync concurrently. Larger number = more responsive statefulsets, but more CPU (and network) load. |
(Appears in: KubeControllerManagerConfiguration)
TTLAfterFinishedControllerConfiguration contains elements describing TTLAfterFinishedController.
| Field | Description |
|---|---|
ConcurrentTTLSyncs
*
int32
|
concurrentTTLSyncs is the number of TTL-after-finished collector workers that are allowed to sync concurrently. |
(Appears in: PersistentVolumeBinderControllerConfiguration)
VolumeConfiguration contains all enumerated flags meant to configure all volume plugins. From this config, the controller-manager binary will create many instances of volume.VolumeConfig, each containing only the configuration needed for that plugin which are then passed to the appropriate plugin. The ControllerManager binary is the only part of the code which knows what plugins are supported and which flags correspond to each plugin.
| Field | Description |
|---|---|
EnableHostPathProvisioning
*
bool
|
enableHostPathProvisioning enables HostPath PV provisioning when running without a cloud provider. This allows testing and development of provisioning features. HostPath provisioning is not supported in any way, won't work in a multi-node cluster, and should not be used for anything other than testing or development. |
EnableDynamicProvisioning
*
bool
|
enableDynamicProvisioning enables the provisioning of volumes when running within an environment that supports dynamic provisioning. Defaults to true. |
PersistentVolumeRecyclerConfiguration
*
PersistentVolumeRecyclerConfiguration
|
persistentVolumeRecyclerConfiguration holds configuration for persistent volume plugins. |
FlexVolumePluginDir
*
string
|
volumePluginDir is the full path of the directory in which the flex volume plugin should search for additional third party volume plugins |
(Appears in: CloudControllerManagerConfiguration, KubeControllerManagerConfiguration)
ServiceControllerConfiguration contains elements describing ServiceController.
| Field | Description |
|---|---|
ConcurrentServiceSyncs
*
int32
|
concurrentServiceSyncs is the number of services that are allowed to sync concurrently. Larger number = more responsive service management, but more CPU (and network) load. |
| Field | Description |
|---|---|
apiVersion string |
cloudcontrollermanager.config.k8s.io/v1alpha1 |
kind string |
CloudControllerManagerConfiguration |
Generic
*
GenericControllerManagerConfiguration
|
Generic holds configuration for a generic controller-manager |
KubeCloudShared
*
KubeCloudSharedConfiguration
|
KubeCloudSharedConfiguration holds configuration for shared related features both in cloud controller manager and kube-controller manager. |
ServiceController
*
ServiceControllerConfiguration
|
ServiceControllerConfiguration holds configuration for ServiceController related features. |
NodeStatusUpdateFrequency
*
meta/v1.Duration
|
NodeStatusUpdateFrequency is the frequency at which the controller updates nodes' status |
(Appears in: KubeCloudSharedConfiguration)
CloudProviderConfiguration contains basically elements about cloud provider.
| Field | Description |
|---|---|
Name
*
string
|
Name is the provider for cloud services. |
CloudConfigFile
*
string
|
cloudConfigFile is the path to the cloud provider configuration file. |
(Appears in: CloudControllerManagerConfiguration, KubeControllerManagerConfiguration)
KubeCloudSharedConfiguration contains elements shared by both kube-controller manager and cloud-controller manager, but not genericconfig.
| Field | Description |
|---|---|
CloudProvider
*
CloudProviderConfiguration
|
CloudProviderConfiguration holds configuration for CloudProvider related features. |
ExternalCloudVolumePlugin
*
string
|
externalCloudVolumePlugin specifies the plugin to use when cloudProvider is "external". It is currently used by the in repo cloud providers to handle node and volume control in the KCM. |
UseServiceAccountCredentials
*
bool
|
useServiceAccountCredentials indicates whether controllers should be run with individual service account credentials. |
AllowUntaggedCloud
*
bool
|
run with untagged cloud instances |
RouteReconciliationPeriod
*
meta/v1.Duration
|
routeReconciliationPeriod is the period for reconciling routes created for Nodes by cloud provider.. |
NodeMonitorPeriod
*
meta/v1.Duration
|
nodeMonitorPeriod is the period for syncing NodeStatus in NodeController. |
ClusterName
*
string
|
clusterName is the instance prefix for the cluster. |
ClusterCIDR
*
string
|
clusterCIDR is CIDR Range for Pods in cluster. |
AllocateNodeCIDRs
*
bool
|
AllocateNodeCIDRs enables CIDRs for Pods to be allocated and, if ConfigureCloudRoutes is true, to be set on the cloud provider. |
CIDRAllocatorType
*
string
|
CIDRAllocatorType determines what kind of pod CIDR allocator will be used. |
ConfigureCloudRoutes
*
bool
|
configureCloudRoutes enables CIDRs allocated with allocateNodeCIDRs to be configured on the cloud provider. |
NodeSyncPeriod
*
meta/v1.Duration
|
nodeSyncPeriod is the period for syncing nodes from cloudprovider. Longer periods will result in fewer calls to cloud provider, but may delay addition of new nodes to cluster. |
(Appears in: GenericControllerManagerConfiguration)
LeaderMigrationConfiguration provides versioned configuration for all migrating leader locks.
| Field | Description |
|---|---|
apiVersion string |
controllermanager.config.k8s.io/v1alpha1 |
kind string |
LeaderMigrationConfiguration |
leaderName
*
string
|
LeaderName is the name of the leader election resource that protects the migration E.g. 1-20-KCM-to-1-21-CCM |
resourceLock
*
string
|
ResourceLock indicates the resource object type that will be used to lock Should be "leases" or "endpoints" |
controllerLeaders
*
[]ControllerLeaderConfiguration
|
ControllerLeaders contains a list of migrating leader lock configurations |
(Appears in: LeaderMigrationConfiguration)
ControllerLeaderConfiguration provides the configuration for a migrating leader lock.
| Field | Description |
|---|---|
name
*
string
|
Name is the name of the controller being migrated E.g. service-controller, route-controller, cloud-node-controller, etc |
component
*
string
|
Component is the name of the component in which the controller should be running. E.g. kube-controller-manager, cloud-controller-manager, etc Or '*' meaning the controller can be run under any component that participates in the migration |
(Appears in: CloudControllerManagerConfiguration, KubeControllerManagerConfiguration)
GenericControllerManagerConfiguration holds configuration for a generic controller-manager.
| Field | Description |
|---|---|
Port
*
int32
|
port is the port that the controller-manager's http service runs on. |
Address
*
string
|
address is the IP address to serve on (set to <IP_ADDRESS> for all interfaces). |
MinResyncPeriod
*
meta/v1.Duration
|
minResyncPeriod is the resync period in reflectors; will be random between minResyncPeriod and 2*minResyncPeriod. |
ClientConnection
*
ClientConnectionConfiguration
|
ClientConnection specifies the kubeconfig file and client connection settings for the proxy server to use when communicating with the apiserver. |
ControllerStartInterval
*
meta/v1.Duration
|
How long to wait between starting controller managers |
LeaderElection
*
LeaderElectionConfiguration
|
leaderElection defines the configuration of leader election client. |
Controllers
*
[]string
|
Controllers is the list of controllers to enable or disable '*' means "all enabled by default controllers" 'foo' means "enable 'foo'" '-foo' means "disable 'foo'" first item for a particular name wins |
Debugging
*
DebuggingConfiguration
|
DebuggingConfiguration holds configuration for Debugging related features. |
LeaderMigrationEnabled
*
bool
|
LeaderMigrationEnabled indicates whether Leader Migration should be enabled for the controller manager. |
LeaderMigration
*
LeaderMigrationConfiguration
|
LeaderMigration holds the configuration for Leader Migration. |
Generated with genref
on git commit 4247aac7


WEEK 30 SUNDAY
Entrance Antiphon
Let the hearts that seek the Lord rejoice; Turn to the Lord and his strength; constantly seek his face.
Collect
Almighty ever-living God, increase our faith, hope and charity, and make us love what you command, so that we may merit what you promise. Through our Lord. . .
Theme of the Sunday: The Whole Law Is Summarised in Love.
The Christian catechism is not difficult; it can all be learnt in one lesson. If we obey the commandment of love we fulfil the whole law. The rest is just comment and explanation. This is the message we learn from the gospel today. The first reading applies this commandment to our less fortunate brothers and sisters, strangers, orphans and widows. The second reading is linked to this theme; it gives the example of the early Christian communities who obeyed the law of love.

A reading from the Book of Exodus
Thus says the LORD: "You shall not wrong a
stranger or oppress him, for you were strangers in the
RESPONSORIAL PSALM Psalm 18:2-3a.3bc-4.47 and 51ab (R. 2)
R. I love you, Lord, my strength.

R. I love you, Lord, my strength.
My God, my rock where I take refuge; my
shield, my saving strength, my stronghold. I cry out, “Praised
be the LORD!” and see, I am saved from my foes.
R. I love you, Lord, my strength.
The LORD lives, and blest be my Rock! May the God
of my salvation be exalted. The LORD gives great
victories to his king, and shown merciful love for his anointed.
R. I love you, Lord, my strength.
SECOND READING 1 Thessalonians 1:5c-10
“You turned from idols to serve God and to wait for his Son.”
A reading from the first Letter of Saint Paul to the Thessalonians
Brethren: You know what kind of men we proved to be
among you for your sake. And you became imitators of us and of the Lord, for
you received the word in much affliction, with joy inspired by the Holy Spirit;
so that you became an example to all the believers in
The word of the Lord
ALLELUIA John 14:23
R. Alleluia. If a man loves me, he will keep my words, says the Lord; and my Father will love him, and we will come to him. R. Alleluia.
GOSPEL Matthew 22:34-40
“You shall love the Lord your God and your neighbour as yourself.”
A reading from the holy Gospel according to Matthew
At that time: When the Pharisees heard that Jesus had
silenced the Sadducees, they came together. And one of them, a lawyer, asked
him a question, to test him. "Teacher, which is the
great commandment in the law?"  This is the great and first commandment.  On these two commandments depend all the law
and the prophets."
The Gospel of the Lord
Theme of the Sunday: Enlightened to Follow Christ.
The episode of the healing of Bartimaeus in the gospel has a lot to teach about the light that the Christian receives when meeting Christ in Baptism. It is in this sacrament that the eyes of men and women are opened. That is where they understand what it means to follow Christ. The first reading prepares this teaching as it describes the journey of the “blind” people of Israel from slavery to freedom. God himself is their guide. The second reading contains words of consolation for those who, after receiving the light of Christ, follow the Master along the road: he is a travelling companion who can understand our weakness.
FIRST READING Jeremiah 31:7-9
“With consolations I will lead them back, among them the blind and the lame.”
A reading from the Book of Jeremiah
Thus says the LORD: "Sing aloud with gladness
for Jacob, and raise shouts for the chief of the nations; proclaim, give
praise, and say, 'The LORD has saved his people, the remnant of
The word of the Lord
RESPONSORIAL PSALM Psalm 126:1-2ab.2cd-3.4-5.6 (R. 3)
R. What great deeds the Lord worked for us! Indeed, we were glad.
When the LORD brought back the exiles of Sion, we
thought we were dreaming.  What great deeds the Lord worked for us! Indeed, we
were glad.
Then the nations themselves said, 'What great deeds
the LORD worked for them!' What great deeds the LORD worked for us! Indeed, we
were glad.
R. What great deeds the Lord worked for us! Indeed, we
were glad.
Bring back our exiles, O LORD, as streams in the
south. Those who are sowing in tears will sing when they reap.
R. What great deeds the Lord worked for us! Indeed, we
were glad.

R. What great deeds the Lord worked for us! Indeed, we
were glad.
SECOND READING Hebrews 5:1-6
“You are a priest for ever, according to the order of Melchizedek.”
A reading from the Letter to the Hebrews
Every high priest chosen from among men is appointed
to act on behalf of men in relation to God, to offer gifts and sacrifices for
sins. He can deal gently with the ignorant and wayward, since he himself is
beset with weakness. Because of this he is bound to offer sacrifice for his own
sins as well as for those of the people. And one does not take the honour upon
himself, but he is called by God, just as Aaron was. So also Christ did not
exalt himself to be made a high priest, but was appointed by him who said to
him, "You are my Son, today I have begotten you"; as he says also in
another place, "You are a priest for ever, according to the order of Melchizedek."
The word of the Lord
ALLELUIA See 2 Timothy 1:10
R. Alleluia. Our Saviour Christ Jesus abolished death and brought life and immortality to light through the Gospel. R. Alleluia.
GOSPEL Mark 10:46-52
“Master, let me receive my sight.”
A reading from the holy Gospel according to Mark
At that time: As Jesus was leaving
The Gospel of the Lord
FIRST READING Sirach 35:12c-14.16-18b
“The prayer of the humble pierces the clouds.”
A reading from the Book of Sirach
The Lord is the judge, and with him is no
partiality. He will not show partiality in the case of a poor man; and he will
listen to the prayer of one who is wronged. He will not ignore the supplication
of the fatherless, nor the widow when she pours out her story. He whose service
is pleasing to the Lord will be accepted, and his prayer will reach to the
clouds. The prayer of the humble pierces the clouds, and he will not be
consoled until it reaches the Lord; he will not desist until the Most High
visits him, and does justice for the righteous, and executes judgment. And the
Lord will not delay, neither will he be patient with
them.
The word of the Lord
RESPONSORIAL PSALM Ps 34:2-3.17-18.19 and 23 (R. cf. 7a)
R. The lowly one called, and the Lord heard him.
I will bless the LORD at all times,
praise of him is always in my mouth. In the LORD my soul shall make its boast;
the humble shall hear and be glad.
R. The lowly one called, and the Lord heard him.
 The just cry out, the LORD hears, and
rescues them in all their distress.
R. The lowly one called, and the Lord heard him.
The LORD is close to the broken-hearted; those whose
spirit is crushed he will save. The LORD ransoms the souls of his servants. All
who trust in him shall not be condemned.
R. The lowly one called, and the Lord heard him.
SECOND READING 2 Timothy 4:6-8.16-18
“From now on there is laid up for me the crown of righteousness.”
A reading from the second Letter of Saint Paul to Timothy
Beloved: I am already on the point of being
sacrificed; the time of my departure has come. I have fought the good fight, I
have finished the race, I have kept the faith.
Henceforth there is laid up for me the crown of righteousness, which the Lord,
the righteous judge, will award to me on that Day, and not only to me but also
to all who have loved his appearing. At my first defence no one took my part;
all deserted me. May it not be charged against them! But the Lord stood by me
and gave me strength to proclaim the message fully, that all the Gentiles might
hear it. So I was rescued from the lion's mouth. The Lord will rescue me from
every evil and save me for his heavenly kingdom. To him be
the glory for ever and ever. Amen.
The word of the Lord
ALLELUIA 2 Corinthians 5:19
R. Alleluia. God was in Christ reconciling the world to himself, and entrusting to us the message of reconciliation. R. Alleluia.
GOSPEL Luke 18:9-14
“The publican went down to his house justified rather than the Pharisee.”
A reading from the holy Gospel according to Luke
At that time: Jesus told this parable to some who
trusted in themselves that they were righteous and despised others: "Two
men went up into the temple to pray, one a Pharisee and the other a tax
collector. The Pharisee stood and prayed thus with himself, 'God, I thank you
that I am not like other men, extortioners, unjust, adulterers, or even like
this tax collector. I fast twice a week, I give tithes
of all that I get.' But the tax collector, standing far off, would not even
lift up his eyes to heaven, but beat his breast, saying, 'God, be merciful to
me a sinner!' I tell you, this man went down to his house justified rather than
the other; for every one who exalts himself will be humbled, but he who humbles
himself will be exalted."
The Gospel of the Lord
Prayer over the Offerings
Look, we pray, O Lord, on the offerings we make to your majesty, that whatever is done by us in your service may be directed above all to your glory. Through Christ our Lord.
Communion Antiphon
We will ring out our joy at your saving help,
and exult in the name of our God.
Or:
Christ loved us and gave himself up for us,
as a fragrant offering to God.
Prayer after Communion
May your Sacraments, O Lord, we pray, perfect in us what lies within them, that what we now celebrate in signs we may one day possess in truth. Through Christ our Lord.


Please add a link
Advanced Statistics
Track how your links are performing across the web with our advanced statistics dashboard.
Brand Recognition
Boost your brand recognition with each click. Generic links don't mean a thing. Branded links help instil confidence in your content.
Detailed Records
Gain insights into who is clicking your links. Knowing when and where people engage with your content helps inform better decisions.
Fully Customizable
Improve brand awareness and content discoverability through customizable links, supercharging audience engagement.


| 接口 | 说明 |
|---|---|
| Processor |
A processor implementation may modify the data belonging to a document.
|
| Processor.Factory |
A factory that knows how to construct a processor based on a map of maps.
|
| ValueSource |
Holds a value.
|
| 类 | 说明 |
|---|---|
| AbstractProcessor |
An Abstract Processor that holds a processorTag field to be used
by other processors.
|
| CompoundProcessor |
A Processor that executes a list of other "processors".
|
| ConfigurationUtils | |
| IngestDocument |
Represents a single document being captured before indexing and holds the source and metadata (like id, type and index).
|
| IngestInfo | |
| IngestMetadata |
Holds the ingest pipelines that are available in the cluster
|
| IngestService |
Holder class for several ingest related services.
|
| IngestStats | |
| IngestStats.Stats | |
| Pipeline |
A pipeline is a list of
Processor instances grouped under a unique id. |
| Pipeline.Factory | |
| PipelineConfiguration |
Encapsulates a pipeline's id and configuration as a blob
|
| PipelineExecutionService | |
| PipelineStore | |
| Processor.Parameters |
Infrastructure class that holds services that can be used by processor factories to create processor instances
and that gets passed around to all
IngestPlugin s. |
| ProcessorInfo | |
| ValueSource.ByteValue | |
| ValueSource.ListValue | |
| ValueSource.MapValue | |
| ValueSource.ObjectValue | |
| ValueSource.TemplatedValue |
| 枚举 | 说明 |
|---|---|
| IngestDocument.MetaData |