[pull] main from metallb:main

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,121 @@
+name:  Bug Report
+description: Report a bug
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for making this bug report.
+
+        Please be aware this is not the place to ask for troubleshooting. Unfortunately
+        troubleshooting LB issues in k8s takes a lot of time and effort
+        that we simply don't have. If your load-balancers aren't working,
+        please don't file an issue unless you have identified a _specific_
+        bug to fix. Otherwise, please ask for help in the `#metallb`
+        channel on the Kubernetes Slack
+
+        ---
+
+  - type: input
+    id: metallb-version
+    attributes:
+      label: MetalLB Version
+      description: |
+        [e.g. 0.13.9, 0.12.0]
+    validations:
+      required: true
+  - type: dropdown
+    id: deployment-method
+    attributes:
+      label: Deployment method
+      description: |
+        The method of deployment of MetalLB.
+      multiple: false
+      options:
+        - "Charts"
+        - "Manifests"
+        - "Operator"
+        - "Not relevant"
+    validations:
+      required: true
+  - type: input
+    id: main-cni
+    attributes:
+      label: Main CNI
+      description: |
+        The primary CNI used in the deployment (e.g. calico, cilium)
+    validations:
+      required: true
+  - type: input
+    id: kubernetes-version
+    attributes:
+      label: Kubernetes Version
+      description: |
+        The version of the cluster metallb is deployed to (e.g. 1.26.3)
+  - type: input
+    id: cluster-distribution
+    attributes:
+      label: Cluster Distribution
+      description: |
+        e.g. kind, rancher, openshift, k3s..
+
+  - type: textarea
+    id: bug-report
+    attributes:
+      label: Describe the bug
+      description: A clear and concise description of what the bug is.
+    validations:
+      required: true
+  - type: textarea
+    id: repro-steps
+    attributes:
+      label: To Reproduce
+      description: |
+        Make sure that if you follow these steps again yourself the bug happens again.
+        Steps to reproduce the behavior:
+      placeholder: |
+        1. Apply the following configuration
+        2. Create the service
+        3. The service does not get an IP assigned
+    validations:
+      required: true
+  - type: textarea
+    id: exp-behaviour
+    attributes:
+      label: Expected Behavior
+      description: A clear and concise description of what you expected to happen.
+    validations:
+      required: true
+  - type: textarea
+    id: add-context
+    attributes:
+      label: Additional Context
+      description: Add any other context about the problem here.
+    validations:
+      required: true
+  - type: checkboxes
+    attributes:
+      label: I've read and agree with the following
+      options:
+        - label: I've checked all open and closed issues and my request is not there.
+          required: true
+        - label: I've checked all open and closed pull requests and my request is not there.
+          required: true
+
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: I've read and agree with the following
+      options:
+        - label: I've checked all open and closed issues and my issue is not there.
+          required: true
+        - label: This bug is reproducible when deploying MetalLB from the main branch
+          required: true
+        - label: I have read the [troubleshooting guide](https://metallb.universe.tf/troubleshooting/) and I am still not able to make it work
+          required: true
+        - label: I checked the logs and MetalLB is not discarding the configuration as not valid
+          required: true
+        - label: I enabled the debug logs, collected the information required from the cluster using the [collect script](https://raw.githubusercontent.com/metallb/metallb/main/troubleshooting/collect.sh) and will attach them to the issue
+          required: true
+        - label: I will provide the definition of my service and the related endpoint slices and attach them to this issue
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Need help?
+    url: https://communityinviter.com/apps/kubernetes/community
+    about: Ask support on the \#metallb slack channel
+  - name: Not sure where to start?
+    url: https://metallb.universe.tf/
+    about: Read the MetalLB documentation
+  - name: Having problems with MetalLB?
+    url: https://metallb.universe.tf/troubleshooting/
+    about: Start from the troubleshooting guide

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,39 @@
+name:  Feature or Enhancement Request
+description: Suggest an idea for MetalLB
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for making this suggestion.
+
+        ---
+  - type: textarea
+    attributes:
+      label: Is your feature request related to a problem?
+      description: A clear and concise description of what the problem is.
+      placeholder: With the current configuration options, I can't express a case where my service is ...
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen. Please start describing what you want to
+       solve, rather than how to solve it. It might be already doable by leveraging the current configuration knobs,
+       or there might be better ways to solve it.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add any other context about the feature request here.
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: I've read and agree with the following
+      options:
+        - label: I've checked all open and closed issues and my request is not there.
+          required: true
+        - label: I've checked all open and closed pull requests and my request is not there.
+          required: true

.github/dependabot.yml

@@ -0,0 +1,10 @@
+version: 2
+updates:
+  - package-ecosystem: gomod
+    directory: /
+    schedule:
+      interval: daily
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: weekly

.github/pull_request_template.md

@@ -1,5 +1,4 @@
-Thanks for sending a pull request! A few things before we get started:
-
+<!-- Thanks for sending a pull request!
 1. If this is your first time, please read the [contributing guide](https://metallb.universe.tf/community/#contributing)
 2. For non-trivial pull requests, please [file an
    issue](https://github.com/metallb/metallb/issues/new) first, and get
@@ -10,3 +9,32 @@ Thanks for sending a pull request! A few things before we get started:
 3. If the PR fixes a particular bug, please include the words "Fixed
    #<issue number>" in the PR text, so that the bug auto-closes when
    the PR is merged.
+-->
+
+**Is this a BUG FIX or a FEATURE ?**:
+
+> Uncomment only one, leave it on its own line:
+>
+> /kind bug
+> /kind cleanup
+> /kind feature
+> /kind design
+> /kind flake
+> /kind failing
+> /kind documentation
+> /kind regression
+
+**What this PR does / why we need it**:
+
+**Special notes for your reviewer**:
+
+**Release note**:
+<!--  Write your release note:
+1. Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required".
+2. Follow the instructions for writing a release note from k8s: https://git.k8s.io/community/contributors/guide/release-notes.md
+3. If no release note is required, just write "NONE".
+-->
+
+```release-note
+
+```