F5Networks / f5-declarative-onboarding

F5 BIG-IP Declarative Onboarding
Apache License 2.0
58 stars 22 forks source link

F5 BIG-IP Declarative Onboarding

Releases Issues

Introduction

F5 BIG-IP Declarative Onboarding uses a declarative model to initially configure a F5 BIG-IP device with all of the required settings to get up and running. This includes system settings such as licensing and provisioning, network settings such as VLANs and Self IPs, and clustering settings if you are using more than one BIG-IP system.

IMPORTANT Beginning with F5 BIG-IP DO 1.8.0, the DO RPM, Postman collection, and checksum files will no longer be located in the /dist directory in this repository. These files can be found on the Release page, as Assets.

Documentation

For documentation on F5 BIG-IP Declarative Onboarding, including download, installation, and usage instructions, see the Declarative Onboarding User Guide.

Example F5 BIG-IP Declarative Onboarding declarations

The Declarative Onboarding documentation contains example declarations you can modify to suit your needs. See the Examples page.

Filing Issues and Getting Help

If you come across a bug or other issue when using BIG-IP Declarative Onboarding, use GitHub Issues to submit an issue for our team. You can also see the current known issues on that page, which are tagged with a purple Known Issue label.

Important: Github Issues are consistently monitored by F5 staff, but should be considered as best effort only and you should not expect to receive the same level of response as provided by F5 Support. Please open a case as described below with F5 if this is a critical issue.

Because BIG-IP Declarative Onboarding versions 1.1.0 and later have been created and fully tested by F5 Networks, they are is fully supported by F5. This means you can get assistance if necessary from F5 Technical Support.

Be sure to see the Support page in this repo for more details and supported versions of BIG-IP Declarative Onboarding.

Copyright

Copyright 2014-2024 F5, Inc.

F5 Networks Contributor License Agreement

Before you start contributing to any project sponsored by F5, Inc. on GitHub, you will need to sign a Contributor License Agreement (CLA).

If you are signing as an individual, we recommend that you talk to your employer (if applicable) before signing the CLA since some employment agreements may have restrictions on your contributions to other projects. Otherwise by submitting a CLA you represent that you are legally entitled to grant the licenses recited therein.

If your employer has rights to intellectual property that you create, such as your contributions, you represent that you have received permission to make contributions on behalf of that employer, that your employer has waived such rights for your contributions, or that your employer has executed a separate CLA with F5.

If you are signing on behalf of a company, you represent that you are legally entitled to grant the license recited therein. You represent further that each employee of the entity that submits contributions is authorized to submit such contributions on behalf of the entity pursuant to the CLA.